public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/42727] New: configure: error: cannot compute suffix of object files: cannot compile
Date: Wed, 13 Jan 2010 13:55:00 -0000 [thread overview]
Message-ID: <bug-42727-10743@http.gcc.gnu.org/bugzilla/> (raw)
While looking to see that my daily build on an older i686 machine was still
working, I discover this. The failure started on 12-7-2009. This is with
trunk updated daily. The machine is running fedora 8.
checking for i686-pc-linux-gnu-gcc... /home/jerry/gcc/objdir/./gcc/xgcc
-B/home/jerry/gcc/objdir/./gcc/ -B/usr/local/gfortran/i686-pc-linux-gnu/bin/
-B/usr/local/gfortran/i686-pc-linux-gnu/lib/ -isystem
/usr/local/gfortran/i686-pc-linux-gnu/include -isystem
/usr/local/gfortran/i686-pc-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/home/jerry/gcc/objdir/i686-pc-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/home/jerry/gcc/objdir'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/jerry/gcc/objdir'
make: *** [all] Error 2
--
Summary: configure: error: cannot compute suffix of object files:
cannot compile
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jvdelisle at gcc dot gnu dot org
GCC host triplet: i686-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42727
next reply other threads:[~2010-01-13 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:55 jvdelisle at gcc dot gnu dot org [this message]
2010-01-13 13:57 ` [Bug bootstrap/42727] " jvdelisle at gcc dot gnu dot org
2010-01-13 14:08 ` hjl dot tools at gmail dot com
2010-01-13 14:33 ` jvdelisle at gcc dot gnu dot org
2010-01-14 3:01 ` jvdelisle at gcc dot gnu dot org
2010-01-14 3:03 ` pinskia at gcc dot gnu dot org
2010-01-14 5:32 ` jvdelisle at gcc dot gnu dot org
2010-01-14 5:33 ` jvdelisle at gcc dot gnu dot org
2010-01-14 19:42 ` David dot Biesack at sas dot com
2010-01-14 19:46 ` pinskia at gcc dot gnu dot org
2010-01-14 20:09 ` David dot Biesack at sas dot com
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-42727-10743@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).