Thankyou, that's both much more and much less than I expected.

Much more, in as much as I wasn't expecting to receive a solution to the question, just hoping for guidance in arriving at one:)

Much less in that I expected there to be considerably more work involved in getting there. The main difference between what you provided and what I had tried was the use of BCC32 for the linker instead of ilink32, and the use of "" for the linker options. Suffice to say, I now have parrot.exe built and the testing is progressing

Test results summary--final

Failed Test     Status Wstat Total Fail  Failed  List of Failed
----------------------------------------------------------------------
+----------
t/op/hacks.t       1   256     9    1  11.11%  7
t/op/string.t      1   256    99    1   1.01%  97
t/src/basic.t    255 65280     2    2 100.00%  1-2
t/src/exit.t     255 65280     2    2 100.00%  1-2
t/src/intlist.t  255 65280     4    4 100.00%  1-4
t/src/list.t     255 65280     2    2 100.00%  1-2
t/src/sprintf.t  255 65280     2    2 100.00%  1-2
21 subtests skipped.
Failed 7/46 test scripts, 84.78% okay. 14/658 subtests failed, 97.87% 
+okay.
NMAKE : fatal error U1077: 'D:\WINNT\system32\cmd.exe' : return code '
+0xff'
Stop.

[download]
Examine what is said, not who speaks.
1) When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
2) The only way of discovering the limits of the possible is to venture a little way past them into the impossible
3) Any sufficiently advanced technology is indistinguishable from magic.
Arthur C. Clarke.

In reply to Re: Re: Parrot build mechanism expertise required. by BrowserUk
in thread Parrot build mechanism expertise required. by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.