[Bug c/32415] libgcc_s not found in library search path with --enable-version-specific-runtime-libs

["jwakely dot gcc at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- 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