Re: MSYS package for Strawberry Perl
[email protected] ("Sisyphus") Thu, 6 Sep 2012 05:22:03 +1000
| Newsgroups | perl.win32.vanilla |
|---|---|
| Message-ID | <2B015F1B64C044199DD9385EDC2B885A@desktop2> |
----- Original Message ----- From: "chm" <[email protected]> To: "kmx" <[email protected]>; "Sisyphus" <[email protected]> Cc: <[email protected]> Sent: Thursday, September 06, 2012 3:52 AM Subject: MSYS package for Strawberry Perl > Hi Rob and kmx- > > I finally got around to setting up an MSYS > install for my windows/SPP work and it was > really nice to finally be able to build a > bunch of those autoconf libraries for SPP > and PDL. > > The catch was that the MSYS was builts with > on version of the MinGW toolchain from the > one in Strawberry Perl and SPP. I think there > would be a great simplification of configuration > and reduction in possible version skew if we > could have an MSYS built from/with the MinGW > toolchain of SP. Chris, my experience has always been that it doesn't matter what toolchain built my MSYS. The MSYS that I currently use was provided with my download of mingw.org's gcc-4.5.2 compiler. Within that shell I've used a variety of mingw compilers to build numerous libraries - both 32-bit and 64-bit (and including the current Strawberry compilers). And that has not thrown up any problems. Of course, I do strike problems from time to time, but I haven't struck any problems related to the tool chain that built MSYS. Is there a specific example that you can relate ? Cheers, Rob