|Welcome to the Monastery|
It's a valid point. The last time I tried MinGW, it was version 2 and I was attempting to build 5.6.1. I downloaded MinGW-3.0.0-rc4 whilst I was sleeping with the intention of trying this out on 5.8.1. I just haven't got to that yet, but will once the glee of having achieved the Borland build begins to wear off.
Essentially, I had gotten much further with Borland previously so it was a no-brainer to try that first this time around. Using MinGW would be preferable in at least some ways to Borland. Having access to the sources of the runtime libraries mean that if (for example) the large file support was missing, then I could more easily correct that than with the Borland stuff. I haven't tried to pull apart and reassemble a .dll in a long time, which is what I would probably need to do to fix the Borland CRT.
Examine what is said, not who speaks."Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.
In reply to Re: Re: Re: Re: Perl / Win32 / VC++ / USE_LARGE_FILES