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: Wed, 22 Jun 2011 09:21:00 -0000	[thread overview]
Message-ID: <bug-49072-4-U4eFEdl0q8@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

--- 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.


  parent reply	other threads:[~2011-06-22  9:21 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
2011-06-21 10:52 ` redi at gcc dot gnu.org
2011-06-22  9:21 ` franck.z.bugzilla at orange dot fr [this message]
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-U4eFEdl0q8@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: link
Be 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).