Re: [wxperl-users] WxPerl 0.06 compilation on Win32

[Mattia B. <mb...@ds...>]

> Sorry for not being quite clear before, we were doing
> perl Makefile.PL USE_SHARED=0
> ..trying again with simply not specifying USE_SHARED at all had the
> same results (it used dlltool, and still broke anyway)
I was _really_ hoping it was that simple...

> > binutils-2.10.91-20010114.zip
> > gcc-2.95.2-20001116.zip
> > ld-2.10.91-20010126.zip
> > libbfd-2.10.91-20010121.zip
> > make-3.77-mingw32.zip
> > mingw-runtime-0.5-20010221.tar.gz
> > mingw32-docs-html.exe
> > w32api-0.5-20010301.tar.gz
> >
> 
> Tried these versions of the packages (well, with w32api 0.4), wxPerl
> compiled fine again, and broke again in the same way. This is really
> wierd. We have no idea what else could be going on here.
Just to be sure, I did a fresh GCC install with these packages
( and w32api/mingw-runtime 0.4 ); after some header moving
( I have the w32api with the wrong packaging scheme... ), it
compiled wxWindows, ( just had to change typedef long INT32; ->
typedef int INT32; in jmorecfg.h ), then did a build
with perl -MConfig_m Makefile.PL in the cvs snapshot you're
using, guess what? all compiled/linked/run fine...

Last chance: send me your build log ( dmake > build.log )
I _now_ remember I had a similar problem: it was caused
by some combination of -mdll -lmsvcrt, or something like this
( the problem is that I don't remember if it happened with ActivePerl
  or perl built from sources, with dlltool or -shared... )
If it is this, it is a bug in Config_m.pm

Thanks
Mattia