This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: g++ 4.1?

Thanks to all that encouragement, I now have not one but two working
installations of gcc-4.1.1.  As Brian said, the cygwin compiler will
configure and make with no problems, except that -mno-cygwin doesn't
work. For a no-cygwin compiler, this is what I did -- I'm not saying
it's a good idea. First ftp your sources from GNU. (I only took
gcc-core and gcc-g++). Use setup to make sure you've got gcc-3.4.5 and
anything with mingw in the package name, and maybe gmp, flex and
bison. (I don't know exactly what is required. It turns out I already
had everything I needed.)

../<...>/configure --disable-nls --program-suffix=<...> \
 --host=i686-pc-cygwin --target=i686-pc-mingw32

## failure; can't find <windows.h>
ln -s /usr/include/w32api /usr/i686-pc-ming32/sys-include # (stupid hack)

## failure; can't find i686-pc-mingw32-ar.exe
for x in as ld ar nm strip ranlib # (stupid hack)
do ln -s /usr/i686-pc-mingw32/bin/$x.exe /usr/bin/i686-pc-mingw32-$x.exe

make install

The resulting compiler does seem to make working native binaries, at
least for my program, which doesn't explicitly use DLLs or exceptions.
Final thought: this probably wasn't worth the trouble.

Regards, Buster.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]