From: Ian Lance Taylor <iant@google.com>
To: Dieter Best <dieterbest@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: ==> build gcc failure: " ... cannot compute suffix ..."
Date: Fri, 26 Mar 2010 02:42:00 -0000 [thread overview]
Message-ID: <mcrsk7nrjfi.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <292034b61003251418l3da66e31m21ddde258cd05ead@mail.gmail.com> (Dieter Best's message of "Thu\, 25 Mar 2010 14\:18\:12 -0700")
Dieter Best <dieterbest@gmail.com> writes:
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
> make[2]: *** [configure-stage1-target-libgcc] Error 1
Take a look at x86_64-unknown-linux-gnu/libgcc/config.log to see what
went wrong.
Ian
next prev parent reply other threads:[~2010-03-26 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 21:41 Dieter Best
2010-03-26 2:42 ` Ian Lance Taylor [this message]
2010-03-26 4:14 ` Dieter Best
2010-03-26 6:48 ` Dieter Best
2010-03-26 12:26 ` Ian Lance Taylor
2010-03-26 20:32 ` Dieter Best
2010-03-26 7:55 ` Sven Eschenberg
2010-03-26 8:53 ` Dieter Best
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=mcrsk7nrjfi.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=dieterbest@gmail.com \
--cc=gcc-help@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).