public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jwakely dot gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/32415] libgcc_s not found in library search path with --enable-version-specific-runtime-libs Date: Mon, 09 Jul 2007 10:30:00 -0000 [thread overview] Message-ID: <20070709103024.24811.qmail@sourceware.org> (raw) In-Reply-To: <bug-32415-14725@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from jwakely dot gcc at gmail dot com 2007-07-09 10:30 ------- I'm seeing the same with this configuration: Using built-in specs. Target: x86_64-redhat-linux Configured with: $SRCS/gcc/gcc-4.1.1/configure --prefix=$DEST/gcc/4.1.1-64bit --with-gnu-as --with-as=$DEST/binutils/2.16.1-64bit/bin/as64 --with-gnu-ld --with-ld=$DEST/binutils/2.16.1-64bit/bin/ld64 --enable-shared --enable-threads=posix --enable-languages=c,c++ --disable-checking --with-system-zlib --enable-__cxa_atexit --enable-version-specific-runtime-libs --host=x86_64-redhat-linux Thread model: posix gcc version 4.1.1 (very long paths substituted for SRCS/DEST for brevity) libgcc_s cannot be found for either 32-bit (-m32) or 64-bit (-m64) builds, because the appropriate one of $PREFIX/lib/gcc/x86_64-redhat-linux/{lib,lib64} isn't in the linker's list of library paths. This only happens for multi-libbed compilers; for a 32-bit-only compiler on the same machine there is no problem, because libgcc_s is in the $PREFIX/lib/gcc/x86_64-redhat-linux/4.1.1 directory, which is always in the linker's search path. Exactly the same problem happens with a multi-libbed 4.1.1 with target sparc64-sun-solaris2.8 -- jwakely dot gcc at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwakely dot gcc at gmail dot | |com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32415
next prev parent reply other threads:[~2007-07-09 10:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-20 11:52 [Bug c/32415] New: " lionelb dot nospam at gmail dot com 2007-06-20 15:31 ` [Bug c/32415] " lionelb dot nospam at gmail dot com 2007-07-09 10:30 ` jwakely dot gcc at gmail dot com [this message] 2007-07-09 10:35 ` jwakely dot gcc at gmail dot com 2007-08-03 23:30 ` jwakely dot gcc at gmail dot com 2008-02-19 18:36 ` Ralf dot Wildenhues at gmx dot de 2008-02-21 15:33 ` rwild at gcc dot gnu dot org 2008-02-21 15:36 ` rwild at gcc dot gnu dot org 2008-06-16 11:13 ` jwakely dot gcc at gmail dot com 2008-06-30 14:18 ` dfranke at gcc dot gnu dot org 2009-07-14 6:35 ` [Bug other/32415] " xenofears at gmail 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=20070709103024.24811.qmail@sourceware.org \ --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: linkBe 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).