http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49072
--- Comment #7 from Franck Z <franck.z.bugzilla at orange dot fr> 2011-06-22
09:21:41 UTC ---
In reply to comment #6)
> > Hope this piece of information is useful. :-)
> Not really, if you don't say which versions of GCC and GMP/MFPR/MPC you're
> using, and your exact configure command, then it's not reproducable or
> verifiable.
My Cygwin is recent (one week old).
I have the same source tree for gcc, gcc/gmp, gcc/mpc and gcc/mpfr as the one
advised here (4.6.0, 4.3.2, 0.9 and 3.0.1).
Along with Cygwin comes:
- libgmp, libgmp3, libgmpxx4 and libgmp-devel 4.3.1-3
- libmpc1 and libmpc-devel 0.8-1
- libmpfr1 and libmpfr-devel 2.4.1-4
I edited /usr/local/include/gmpxx.h to added "choke me" in order to verify if
it's used by gcc's "make" despite gmp's source being in my source tree.
gcc output is in an "objdir" directory separate from my gcc source directory.
Configure script (after a "make distclean" command in "objdir"), with "objdir"
as my present working directory :
/"path to my source"/configure --enable-cx
then:
make
That's the configuration I'm testing now ("make" isn't finished). The first
build failures I refer too were done with pretty much the same configuration,
but for a trunk version of gcc and a one-two months old Cygwin. As I've lost
track of this precise configuration, I'm trying again with the configuration
described above.
> It also seems to be completely unrelated to this bug report, which is about
> segfaults (almost certainly due to faulty hardware) not incorrectly-detected
> system properties during configuration.
I won't fight on this point, ;-).
If my bug shows up again, I'll submit a specific bug report, so as not to
pollute this one.
Thank you.
