On Wed, 22 Oct 2003, Sisyphus wrote:
MSYS 1.0.8(0.46/3/2) 2002-09-07 16:04 i686 unknown; targ=MINGW32 GNU bash, version 2.04.0(1)-release (i686-pc-msys); ENV=/home/greg/.bashrc GNU Make version 3.79.1,Built for i686-pc-msys; MAKE_MODE=unix gcc.exe (GCC) 3.2 (mingw special 20020817-1); targ=MINGW32 GNU ld version 2.13 764208 Sat Sep 07 17:11:20 2002 /bin/msys-1.0.dll 1125488 Sat Sep 07 17:11:18 2002 /usr/bin/make.exe 87040 Sat Sep 07 16:37:58 2002 /mingw/bin/gcc.exe 557056 Sat Sep 07 16:38:02 2002 /mingw/bin/ld.exe
I had first tried building with MingW-2.0.0-3, but struck trouble (can't recall exactly what) so immediately then followed the Readme.win32 (of the day) instructions rigorously - and things ran smoothly.
Out of interest I just ran a '--v' on the gcc that came with that version of mingw and got this:
D:\bbs>/mingw/bin/gcc --v
Reading specs from /mingw/lib/gcc-lib/mingw32/3.2/specs
Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=f77,c++,objc,ada --disable-win32-registry --disable-shared
Thread model: win32
gcc version 3.2 (mingw special 20020817-1)
It bears some resemblance to the gcc that you used.
I see you've retained the '-g' switch in the optimise flags. That should mean that your perl.exe and perl58.dll are quite large, in comparison to my perl.exe (10.4 kb) and my perl58.dll (1.12 mb). The same files on ActiveState builds are, I think, even smaller than mine. What, if any, effect on performance that '-g' switch has, I really wouldn't know. All I know is that, for me at least, it bloated those files.
The gcc that I ultimately used came from: ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/
I've only just now realised that the info in Readme.win32 has changed from when I first built perl with gcc - and no longer refers to that site, but instead refers one directly to MingW. So people might find it hard to make sense of some of my statements in this thread - those which were based on the false belief that 'Readme.win32' had not changed significantly with recent perl releases. (I suspect that there's nothing to be gained from sticking to gcc-2.95.2.)
If you want to get 'Encode' working with 5.8.1 I think it would be worth trying AS sources (when they get to develop a 5.8.1 build).
Many thanks for the info. I find it interesting.
Cheers, Rob
--
Any emails containing attachments will be deleted from my ISP's mail server before I even get to see them. If you wish to email me an attachment, please provide advance warning so that I can make the necessary arrangements.
_______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs