----- Original Message ----- From: "Malcolm Nooning" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Sunday, November 26, 2006 8:33 AM Subject: Success, I think, after modification, with perl v5.8.8 build 819
> Hello, > > I did a new install of perl v5.8.8 build 819 [267479] > > I then obtained the PAR 0.960 and, as I use the MinGW compiler, I did > perl -MConfig_m Makefile.PL Generally speaking, with build 819 and the MinGW compiler, it's unnecessary to use ExtUtils::FakeConfig (-MConfig_m). You can just run 'perl Makefile.PL' and (as long as MinGW\bin is in the path) the rest is taken care of automatically. However, I'm not sure if that will work when it comes to building PAR-0.960. This is just idle curiosity on my part, but I also wonder what (if any) difference it makes if you run: nmake clean set perl5opt=-Mconfig_m perl Makefile.PL nmake test Setting the perl5opt value like that will mean that *every* time 'perl' is run it's run as 'perl -MConfig_m'. I *think* that would mean that those "Set up gcc environment ...." messages (which arise when ActivePerl autodetects the presence of the MinGW compiler) would disappear - but I'm not sure about that. There may be other differences/problems, too. To unset perl5opt you can just run: set perl5opt= (but you probably already knew that.) With build 819 and MinGW, does 'perl -V:ld' still report 'gcc' ? and does 'perl -V:lib_ext' still report '.lib' ? (ExtUtils::FakeConfig-0.08 sets them more appropriately to 'g++' and '.a' respectively.) Cheers, Rob
