public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/32398] New: checking for suffix of object files... configure: error: cannot compute suffix of f object files: cannot compile
Date: Tue, 19 Jun 2007 02:00:00 -0000 [thread overview]
Message-ID: <bug-32398-276@http.gcc.gnu.org/bugzilla/> (raw)
checking for hppa64-hp-hpux11.11-gcc... /test/gnu/gcc/objdir/./gcc/xgcc
-B/test/
gnu/gcc/objdir/./gcc/ -B/opt/gnu64/gcc/gcc-4.3.0/hppa64-hp-hpux11.11/bin/
-B/opt
/gnu64/gcc/gcc-4.3.0/hppa64-hp-hpux11.11/lib/ -isystem
/opt/gnu64/gcc/gcc-4.3.0/
hppa64-hp-hpux11.11/include -isystem
/opt/gnu64/gcc/gcc-4.3.0/hppa64-hp-hpux11.1
1/sys-include
checking for suffix of object files... configure: error: cannot compute suffix
o
f object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage2-target-libgcc] Error 1
make[2]: Leaving directory `/test/gnu/gcc/objdir'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/test/gnu/gcc/objdir'
make: *** [bootstrap] Error 2
Mon Jun 18 21:08:30 EDT 2007
--
Summary: checking for suffix of object files... configure: error:
cannot compute suffix of f object files: cannot compile
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: regression
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: danglin at gcc dot gnu dot org
GCC build triplet: hppa64-hp-hpux11.11
GCC host triplet: hppa64-hp-hpux11.11
GCC target triplet: hppa64-hp-hpux11.11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32398
next reply other threads:[~2007-06-19 2:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 2:00 danglin at gcc dot gnu dot org [this message]
2007-06-19 2:39 ` [Bug regression/32398] " danglin at gcc dot gnu dot org
2007-06-21 23:09 ` [Bug regression/32398] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-06-21 23:49 ` danglin at gcc dot gnu dot org
2007-06-29 18:48 ` mmitchel at gcc dot gnu dot org
2007-07-02 18:12 ` danglin at gcc dot gnu dot org
2007-07-02 18:17 ` [Bug middle-end/32398] " pinskia at gcc dot gnu dot org
2007-07-02 20:08 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-02 20:23 ` pinskia at gcc dot gnu dot org
2007-07-07 20:30 ` danglin at gcc dot gnu dot org
2007-07-07 22:02 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-07 22:41 ` zadeck at naturalbridge dot com
2007-07-07 23:30 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-08 0:58 ` zadeck at naturalbridge dot com
2007-07-08 2:30 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-08 2:41 ` zadeck at naturalbridge dot com
2007-07-08 5:12 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-09 16:31 ` bonzini at gnu dot org
2007-07-09 21:04 ` bonzini at gnu dot org
2007-07-09 22:02 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-09 22:28 ` zadeck at naturalbridge dot com
2007-07-10 0:04 ` dave at hiauly1 dot hia dot nrc dot ca
2007-07-15 17:19 ` danglin at gcc dot gnu dot org
2007-07-15 17:23 ` danglin 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=bug-32398-276@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).