----- Original Message ----- From: "Mark Dootson" <[email protected]>
> I build using ExtUtils::FakeConfig and my own Config_w64.pm I've used that before with the x86 builds, back in the days when it was the only way to be able to use mingw with ActivePerl. It's very good - in fact I still use it to build some 5.8.x ppm packages on ActivePerl-5.8.0 (as that build of perl pre-dates ActiveState's automatic integration of mingw). > > Inline builds OK for me with this setup - the only test failure is in > the taint tests. I've never figured out precisely why (taint tests > always fail - not just the ones in Inline) but have just assumed its > either PERL5OPT=-MConfig_w64 or the setting of @INC do in my > sitecustomize.pl Excellent ! - it's encouraging to know that the glitches I've come up against *aren't* inevitable. > I install ExtUtils::FakeConfig and ensure it creates libperl5xx.a during > the 'dmake install' step. Interestingly, the creation of libperl5xx.a is not necessary with all-but-ancient versions of 32-bit gcc, as the recent versions (beginning with gcc-3.0.0, I think) are quite capable of linking to perl5xx.lib. However, that seems to be the case only with the x86 builds. With x64 builds, mingw64 is again unable to link to perl5xx.lib - so, again, we find the need to create a libperl5xx.a. Actually, in my patches, I've simply linked to perl5xx.dll instead of creating a libperl5xx.a. Jan will probably choke when he gets to that bit ... and I wonder if it might be the source of the strangeness I encountered. (Won't be hard to check if that *is* the culprit.) > You could then maybe see if this approach works and it would help in > tracking down your test failures. Definitely - hopefully I can find time to get onto this today. Thanks muchly for your thoughts - and for sending the config file. Cheers, Rob _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
