public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43858] [4.6 Regression] Bootstrap failure for powerpc-apple-darwin9: cannot compute suffix of object files
Date: Wed, 28 Apr 2010 08:50:00 -0000	[thread overview]
Message-ID: <20100428085016.3507.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43858-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from dominiq at lps dot ens dot fr  2010-04-28 08:50 -------
> Two questions - are you sure you didn't reverse the _w and _f files (i.e. maybe
> _f is the working version and _w the failing one)?  

I have looked at how I have generated the archive and I don't think so.
I'll double-check later today.

> Are you sure this isn't a problem with your 4.0.1 bootstrap compiler? 

How can anyone be sure!-(however this does not seem consistent with
the fact that the all the object files, but  ifcvt.o, have the same size (is
there a way to make a deeper comparison?) and also the regress bot is
still failing to bootstrap (see pointer in comment #0) while using a 
different config (but probably the same gcc).

> Can you try building a different
> working gcc (e.g. from the 4.5 branch), and bootstrapping with that?

I'll try to have a look later today.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43858


  parent reply	other threads:[~2010-04-28  8:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 20:53 [Bug bootstrap/43858] New: " dominiq at lps dot ens dot fr
2010-04-23 12:34 ` [Bug bootstrap/43858] " rguenth at gcc dot gnu dot org
2010-04-23 22:08 ` dominiq at lps dot ens dot fr
2010-04-23 22:16 ` lacombar at gmail dot com
2010-04-25 14:31 ` dominiq at lps dot ens dot fr
2010-04-25 14:40 ` ebotcazou at gcc dot gnu dot org
2010-04-25 15:40 ` dominiq at lps dot ens dot fr
2010-04-26  9:16 ` dominiq at lps dot ens dot fr
2010-04-26 12:11 ` bernds at codesourcery dot com
2010-04-26 12:28 ` dominiq at lps dot ens dot fr
2010-04-26 12:56 ` bernds at codesourcery dot com
2010-04-26 13:16 ` dominiq at lps dot ens dot fr
2010-04-26 13:19 ` bernds at codesourcery dot com
2010-04-26 16:26 ` dominiq at lps dot ens dot fr
2010-04-26 22:54 ` bernds at codesourcery dot com
2010-04-27  9:39 ` dominiq at lps dot ens dot fr
2010-04-27  9:47 ` bernds at gcc dot gnu dot org
2010-04-27 15:25 ` dominiq at lps dot ens dot fr
2010-04-27 15:27 ` dominiq at lps dot ens dot fr
2010-04-27 22:27 ` bernds at gcc dot gnu dot org
2010-04-28  8:50 ` dominiq at lps dot ens dot fr [this message]
2010-04-28  8:54 ` dominiq at lps dot ens dot fr
2010-04-28 13:20 ` dominiq at lps dot ens dot fr
2010-04-28 13:59 ` bernds at codesourcery dot com
2010-04-28 16:50 ` howarth at nitro dot med dot uc dot edu
2010-04-28 17:08 ` dominiq at lps dot ens dot fr
2010-04-28 19:27 ` dominiq at lps dot ens dot fr
2010-04-28 19:33 ` bernds at codesourcery dot com
2010-04-29 11:05 ` bernds at gcc dot gnu dot org
2010-04-29 15:11 ` rguenth at gcc dot gnu dot org
     [not found] <bug-43858-4@http.gcc.gnu.org/bugzilla/>
2011-05-02 14:17 ` uweigand 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=20100428085016.3507.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).