public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amitshah at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/46016] New: libgcc build failure for libmpc installation not in /usr
Date: Thu, 14 Oct 2010 12:07:00 -0000 [thread overview]
Message-ID: <bug-46016-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46016
Summary: libgcc build failure for libmpc installation not in
/usr
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: amitshah@gmx.net
Building gcc out-of-tree from latest svn checkout (r165458).
configure line:
~/src/gcc/configure --prefix=/home/amit/install/gcc
Installing libmpc from sources either in my home dir or in /usr/local produces
the following error (in case of installation in home dir, I appended
--with-mpc=/home/amit/install/mpc
--with-mpc-include=/home/amit/install/mpc/include
--with-mpc-lib=/home/amit/install/mpc/lib to the configure line):
checking for x86_64-unknown-linux-gnu-gcc... /home/amit/build/gcc/./gcc/xgcc
-B/home/amit/build/gcc/./gcc/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/bin/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/include -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/home/amit/build/gcc/x86_64-unknown-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
The config.log snippet is:
gcc version 4.6.0 20101014 (experimental) (GCC)
configure:3004: $? = 0
configure:2993: /home/amit/build/gcc/./gcc/xgcc -B/home/amit/build/gcc/./gcc/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/bin/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/include -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/sys-include -V >&5
xgcc: error: unrecognized option '-V'
xgcc: fatal error: no input files
compilation terminated.
configure:3004: $? = 1
configure:2993: /home/amit/build/gcc/./gcc/xgcc -B/home/amit/build/gcc/./gcc/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/bin/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/include -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/sys-include -qversion >&5
xgcc: error: unrecognized option '-qversion'
xgcc: fatal error: no input files
compilation terminated.
configure:3004: $? = 1
configure:3020: /home/amit/build/gcc/./gcc/xgcc -B/home/amit/build/gcc/./gcc/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/bin/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/include -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/sys-include -o conftest -g
-O2 conftest.c >&5
/home/amit/build/gcc/./gcc/cc1: error while loading shared libraries:
libmpc.so.2: cannot open shared object file: No such file or directory
configure:3023: $? = 1
configure:3211: checking for suffix of object files
configure:3233: /home/amit/build/gcc/./gcc/xgcc -B/home/amit/build/gcc/./gcc/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/bin/
-B/home/amit/install/gcc/x86_64-unknown-linux-gnu/lib/ -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/include -isystem
/home/amit/install/gcc/x86_64-unknown-linux-gnu/sys-include -c -g -O2
conftest.c >&5
/home/amit/build/gcc/./gcc/cc1: error while loading shared libraries:
libmpc.so.2: cannot open shared object file: No such file or directory
configure:3237: $? = 1
next reply other threads:[~2010-10-14 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 12:07 amitshah at gmx dot net [this message]
2010-10-14 13:45 ` [Bug driver/46016] " rguenth at gcc dot gnu.org
2010-10-14 13:51 ` redi 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=bug-46016-4@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).