public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kai.extern at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/37079] cannot find -lgcc_s
Date: Fri, 23 Dec 2011 16:32:00 -0000 [thread overview]
Message-ID: <bug-37079-4-yPmlIqh6Kg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-37079-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37079
Kai Henningsen <kai.extern at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kai.extern at gmail dot com
--- Comment #9 from Kai Henningsen <kai.extern at gmail dot com> 2011-12-23 16:12:17 UTC ---
I am seeing something very like this on x86_64-linux-gnu (native), gcc 4.6.2.
The compiler (with --disable-bootstrap) builds and installs into the prefix,
but then ld is unable to find libgcc_s, because the directory it is installed
in is not in the search path. It is installed into
$(prefix)/lib/gcc/$(target)/lib64.
Complete configure options (including some only relevant for different
packages; from config.log):
$(src)/gcc/configure --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--prefix=$(prefix) --disable-bootstrap --disable-libgomp --disable-libmudflap
--disable-libquadmath --disable-libssp --disable-multilib --disable-nls
--enable-cxx --enable-decimal-float=no --enable-maintainer-mode
--enable-optimization --enable-pch --enable-rpath
--enable-version-specific-runtime-libs --with-bits=gmp --with-gnu-as
--with-gnu-ld --with-ppl --enable-languages=c,c++ --with-gmp=$(prefix)
--with-mpfr=$(prefix) --with-mpc=$(prefix) --with-ppl=$(prefix)
--with-cloog=$(prefix) --target=x86_64-linux-gnu
Other coments: Ubuntu, I'm symlinking all system libs into
$(prefix)/$(target)/lib before I start.
The actual path searched is:
$(prefix)/lib/gcc/x86_64-linux-gnu/4.6.2/
$(prefix)/lib/gcc/x86_64-linux-gnu/4.6.2/../../../../lib64/
/lib/../lib64/
/usr/lib/../lib64/
$(prefix)/lib/gcc/x86_64-linux-gnu/4.6.2/../../../../x86_64-linux-gnu/lib/
$(prefix)/lib/gcc/x86_64-linux-gnu/4.6.2/../../../
$(prefix)/x86_64-linux-gnu/lib64/
$(prefix)/lib64/
/usr/local/lib64/
/lib64/
/usr/lib64/
$(prefix)/x86_64-linux-gnu/lib/
$(prefix)/lib/
/usr/local/lib/
/lib/
/usr/lib/
next parent reply other threads:[~2011-12-23 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-37079-4@http.gcc.gnu.org/bugzilla/>
2011-12-23 16:32 ` kai.extern at gmail dot com [this message]
2011-12-23 17:42 ` redi at gcc dot gnu.org
2008-08-11 9:29 [Bug c/37079] New: " jayk123 at hotmail dot com
2008-08-16 22:38 ` [Bug bootstrap/37079] " pinskia at gcc dot gnu dot org
2008-08-17 8:52 ` jay dot krell at cornell dot edu
2008-08-17 8:53 ` jay dot krell at cornell dot edu
2009-12-09 2:00 ` 3dw4rd at verizon dot net
2009-12-09 4:22 ` howarth at nitro dot med dot uc dot edu
2009-12-09 13:22 ` 3dw4rd at verizon dot net
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-37079-4-yPmlIqh6Kg@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).