public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "franck.z.bugzilla at orange dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/49072] Error building the compiler Date: Tue, 21 Jun 2011 10:32:00 -0000 [thread overview] Message-ID: <bug-49072-4-kqIVj4ODbz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49072-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49072 Franck Z <franck.z.bugzilla at orange dot fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |franck.z.bugzilla at orange | |dot fr --- Comment #5 from Franck Z <franck.z.bugzilla at orange dot fr> 2011-06-21 10:31:45 UTC --- (In reply to comment #4) During my first attempts to compile gcc, I also encountered problem with in-tree compilation of GMP/MPFR/MPC, up to the point that I used the compiled (but not up-to-date) version provided with the Cygwin distribution. It took then place with the trunk. Amont the weird things I observed stood out: - a file "gmpxx.h" could be found and stopped compilation (with or without --enable-xx flag in gcc's configure script) - the architecture recognized by gmp's configure script was different when this script was launched by me ("pentium4-"-something from what I recall...) or by gcc's makefile. When with gcc's makefile, gmp opted for a cross-compilation for i686-pc-cygwin to none-pc-cygwin - although my gcc build was native. About the architecture point, I can't tell much. But about the gmpxx.h file, I suspect that it is a mostly silent bug and that a file /usr/local/include/gmpxx.h provided by Cygwin is used if present. Apparently, gmp's scripts create a gmp.h file when configure is run, but the gmpxx.h wrapper is copied only when a command "make install" is issued, so that gcc multi-stage compilation process may not have it, and this as soon as mpfr (or mpc, I can't remember) needs to link to gmp. The failure telling that gmpxx.h was missing occured during a configure script in mpfr (or mpc, again). When the unavailability of gmpxx.h was by-passed by a local installation of gmp from Cygwin, I also got a division by zero error or such later in the build process. I'm trying to confirm it with 4.6.0 release. I've added a "choke me" line at the beginning of /usr/local/include/gmpxx.h. Right now, the gcc "make" command is running (it's entered "configuring stage 1 in ./gmp"). It may take time before I can get an answer. Hope this piece of information is useful. :-) I can't propose a patch for this if it confirms, for want of skills in makefiles as big as gcc's.
next prev parent reply other threads:[~2011-06-21 10:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-19 21:11 [Bug bootstrap/49072] New: " Jose.Pascual-Gutierr@1-ACT.com 2011-05-19 22:50 ` [Bug bootstrap/49072] " redi at gcc dot gnu.org 2011-05-20 14:07 ` Jose.Pascual-Gutierr@1-ACT.com 2011-05-20 21:42 ` Jose.Pascual-Gutierr@1-ACT.com 2011-06-09 3:45 ` hp at gcc dot gnu.org 2011-06-21 10:32 ` franck.z.bugzilla at orange dot fr [this message] 2011-06-21 10:52 ` redi at gcc dot gnu.org 2011-06-22 9:21 ` franck.z.bugzilla at orange dot fr 2011-06-22 11:08 ` franck.z.bugzilla at orange dot fr 2011-06-22 11:20 ` redi at gcc dot gnu.org 2013-11-10 5:57 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-49072-4-kqIVj4ODbz@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).