I've built 5.8.0 using cygwin. Built and tested, out of the box. There was a complaint in the test about some *dbm problem that I didn't track down.

What's wrong with using cygwin? AFAICT, it's the best way to get a large set of CPAN modules working straight away. Most of the XS stuff has to be massaged for the VC builds and I would imagine this is the case with the Borland compiler as well. If you had a body of Perl that you needed to deploy on Unix and you wanted to do some development on W2K, I'd say that cygwin would be the way to go.

Now, if you require a lot of Win32 modules that were developed under VC, I can see that, but, generally, I have few problems with cygwin.

In reply to Re: Re: Compiling 5.8.0 on Win2K by jordanh
in thread Compiling 5.8.0 on Win2K by Adambomb

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.