public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/41245] [4.5 Regression] Bootstrap broken on I386-apple-darwin9 at revision 151373
Date: Tue, 08 Sep 2009 07:09:00 -0000 [thread overview]
Message-ID: <20090908070932.13625.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41245-10259@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from developer at sandoe-acoustics dot co dot uk 2009-09-08 07:09 -------
(In reply to comment #6)
> I believe Mike Stump told me that it is possible that darwin's strip could
> re-order the sections. Is that possibility addressed in the current patches?
I don't believe re-ordering sections is the solution, in this case.
> Current x86_64-apple-darwin10 has no problems with gcc trunk at the moment.
can you confirm that the top level config produces lines like:
target-libmudflap target-libada gnattools target-libffi target-zlib
target-libjava zlib target-boehm-gc
(Any other directories should still work fine.)
THIS ONE >>> checking for default BUILD_CONFIG... bootstrap-debug
checking for bison... bison -y
and that the build produces:
rm -f stage_current
Comparing stages 2 and 3
warning: gcc/cc1-checksum.o differs
warning: gcc/cc1obj-checksum.o differs
warning: gcc/cc1objplus-checksum.o differs
warning: gcc/cc1plus-checksum.o differs
THIS ONE >>>> Comparison successful.
--
developer at sandoe-acoustics dot co dot uk changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |developer at sandoe-
| |acoustics dot co dot uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41245
next prev parent reply other threads:[~2009-09-08 7:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 13:57 [Bug bootstrap/41245] New: " fxcoudert at gcc dot gnu dot org
2009-09-03 15:24 ` [Bug bootstrap/41245] " howarth at nitro dot med dot uc dot edu
2009-09-03 15:32 ` jakub at gcc dot gnu dot org
2009-09-06 22:14 ` rguenth at gcc dot gnu dot org
2009-09-06 23:00 ` rguenth at gcc dot gnu dot org
2009-09-07 13:10 ` gerald at pfeifer dot com
2009-09-07 13:50 ` developer at sandoe-acoustics dot co dot uk
2009-09-07 15:43 ` howarth at nitro dot med dot uc dot edu
2009-09-07 16:00 ` dominiq at lps dot ens dot fr
2009-09-08 7:09 ` developer at sandoe-acoustics dot co dot uk [this message]
2009-09-08 8:54 ` developer at sandoe-acoustics dot co dot uk
2009-09-08 13:28 ` howarth at nitro dot med dot uc dot edu
2009-09-08 13:41 ` developer at sandoe-acoustics dot co dot uk
2009-09-08 13:52 ` howarth at nitro dot med dot uc dot edu
2009-09-08 14:08 ` developer at sandoe-acoustics dot co dot uk
2009-09-08 14:45 ` developer at sandoe-acoustics dot co dot uk
2009-09-08 23:14 ` howarth at nitro dot med dot uc dot edu
2009-09-09 2:00 ` howarth at nitro dot med dot uc dot edu
2009-09-10 14:33 ` jakub at gcc dot gnu dot org
2009-09-18 9:07 ` rguenth at gcc dot gnu dot org
2009-09-18 12:56 ` developer at sandoe-acoustics dot co dot uk
2009-09-18 13:16 ` howarth at nitro dot med dot uc dot edu
2009-09-27 10:11 ` fxcoudert at gcc dot gnu dot 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=20090908070932.13625.qmail@sourceware.org \
--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).