Hi,
Just to confirm it is a different problem:
C:\strawberry>perl -MConfig -e"print $Config{cc};"
gcc
C:\strawberry>perl -MConfig -e"print $Config{ccname};"
gcc
Regards
Mark
herbert breunung wrote:
yes confirming , yesterday i was compiling Wx on Stawberry 5.10.0.1 and
after 20 min it spew tons of errors.
i first thought it was fault on Strawberrys side but not i also tend to
look for error on Wxperl.
blessings
herbert
Hi,
The recent changes to Alien-wxWidgets breaks correct operation of
ExtUtils::FakeConfig.
This concerns building Alien on Win32 using MinGW, against a non
ActiveState Perl where Perl itself was built using VC6.
It would break an ActiveState build too if it is an older version and
you are using ExtUtils::FakeConfig.
Solution is to fix ExtUtils::FakeConfig.
ExtUtils::FakeConfig installation also needs updating for Perl 5.10.
As I'm building stuff against non ActiveState VC6 versions of Perl 5.8
and 5.10, I will work on a patch for ExtUtils::FakeConfig as it'll be
easiest for me to test. I think the Perl 5.10 stuff will be trivial
(the cc_name bit certainly is) I just won't get to it today.
In the meantime, if anyone else out there is still using
ExtUtils::FakeConfig, just update your installed Config_m.pm to
include "ccname='gcc'".
F.Y.I. I use my own basic builds of Perl built using VC6 to support
the PPMs. Releases of ActivePerl sometimes break compatibility with
prior releases when they include maintenance patches - especially with
5.8 being quite 'venerable', so to ensure that the PPMs are fine for
all recent releases and going forward, I build them against original
source for 5.8.8 and 5.10.0.
(It so happens that the 5.8.8 build works fine for 5.8.4 onwards -
though that's a happy coincidence for me and there is nothing in the
Perl release process that says it should be so).
Mark
