On 17/02/2013 10:38 PM, Zach Saw wrote:
The following test case fails on Cygwin but passes on Linux (both tested using
GCC 4.7.2).
Cygwin doesn't have a gcc-4.7.2 package yet (not even for testing);
4.5.3 is the highest I see this morning in setup.exe.
If you got it from ports, you need to ping their mailing list. If you
built it yourself, we'll need to know how you built it.
Meanwhile, WJJFM with my home-brew 4.7.1:
../src/gcc-4.7.1/configure --prefix=/home/Ryan/apps/gcc-4.7
--enable-bootstrap --enable-version-specific-runtime-libs
--enable-static --enable-shared --enable-shared-libgcc
--disable-__cxa_atexit --with-dwarf2 --disable-sjlj-exceptions
--enable-languages=c,c++,lto --enable-lto --enable-libssp
--enable-threads=posix
Note 1: I've had TLS problems in the past, usually caused by my gcc-4.7
install colliding with the cygwin 4.5.3 install (that
--enable-version-specific-runtime-libs configure flag is really important).
Note 2: I got the above configure incantation by passing -v to cygwin's
official gcc (I figure they know what they're doing).
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
