NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I wish I could say all is well, but... (Score:2)
test COSIMO/Win32-API-0.46.tar.gzin the CPAN shell on the two platforms I have available, and it kind of works... but both seem to fall over a secundary test somewhere. The same one.And notice how it goes searching for the wrong compiler: "cl", not "gcc", as
perl -V:ccdoes say:Again, final verdict is "OK", despite a "freed to the wrong pool" error, which sounds very serious to me. Also notice the message "
Test returned status 5 (wstat 1280, 0x500) after all the subtests completed successfully".And, once more, the compiler it tried to use is wrong again: "icl" — most likely the compiler PXPerl was built with (an Intel compiler, IIRC), but not the compiler that
perl -V:ccreports back ("gcc").There sure is a pattern there: it seems to me like something here is trying too hard to find out the "truth" about the C compiler, ignoring the more obvious results.
Reply to This
Re: (Score:1)
Hi Bart, this is interesting. Thanks for your time.
AFAIK, ActivePerl comes compiled by MSVC6, which is cl.exe version 12, but you are using with gcc. Correct?
In the Callback tests, which btw fail unless you have MSVC6, I needed a way to check the compiler and I used
$Config{ccname}and$Config{ccversion}instead of only using$Config{cc}, because I only must distinguish between MSVC 6 and 7+.Can you report your cc, ccname and ccversion variables? Or better, file a bug on