From: D.J.Moon <lm...@es...> - 2001-05-03 14:38:49
|
----- Original Message ----- From: "Mattia Barbon" <mb...@ds...> To: <wxp...@li...> Sent: Wednesday, May 02, 2001 5:07 PM Subject: Re: [wxperl-users] WxPerl 0.06 compilation on Win32 > > wxPerl 0.06 source tarball > > wxWindows 2.26 > > Win2000 Version 5.00.2195 > > > > "gcc -v" lists gcc version as: > > Reading specs from > > c:\gcc-2.95.2-1\bin\..\lib\gcc-lib\mingw32\2.95.2\specs gcc driver > > version 2.95.2 19991024 (release) executing gcc version 2.95.2-mingw > > snapshot 20010329 > I use a different one: > ---- > Reading specs from C:\Programmi\Devel\GCC\bin\..\lib\gcc- > lib\mingw32\2.95.2\specs > gcc driver version 2.95.2 19991024 (release) executing gcc version > 2.95.2-20001116 > ---- > but maybe it is an ld / libbfd problem... > Okay, we tried using the new USE_SHARED option in the cvs (grabbed using cvs, not the nightly zip, (since you wanted to know)) copy, but that did not make a difference (i.e. still get the same error on "dmake test"). We think that maybe trying to get a mingw setup more closely identical to yours may be the next thing to try. Part of the problem may be incorrect/incompatible versions of the various mingw packages, and part of the problem may simply be that we aren't unpacking them all together quite correctly. To at least make sure that we are trying to work with the same versions, we'd like to know (if you could) what versions/dates of the various mingw packages you use. The packages that we have been downloading are the following: binutils gcc (but we already know you're using gcc-2.95.2-20001116) ld libbfd mingw-runtime w32api (We have been using 0.4 of mingw-runtime and w32api, to avoid having to go through the trouble of needing to patch the wxWindows source.) |