Building with GCC-3.0.3
Frank Schafer
frank.schafer@setuza.cz
Tue Feb 19 02:02:00 GMT 2002
Hi there,
This is my first attempt to build something with a secondary installed
gcc.
I've built gcc3.0.3 and installed it ( --prefix ) in /v_dsk/gcc-new.
Now I've tried to compile something ( db-3.3.11 ) with it.
I did the following steps:
# export CC=/v_dsk/gcc-new/bin/gcc
# configure
# make
... a lot of output, and then:
all the libtool invocations give me something like this
creating db_verify
/bin/sh ./libtool --mode=execute true db_verify
/usr/bin/ld: warning: libgcc_s.so.1, needed by
./.libs/libdb-3.3.so, not found (try using -rpath or
-rpath-link)
The former build of this lib ( with gcc-2.95.3 ) succeeded, and
# ldd /usr/local/lib/libdb-3.3.so
libc.so.6 => /lib/libc.so.6 (0x40089000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
... but
# ldd ./.libs/libdb-3.3.so
libgcc_s.so.1 => not found
libc.so.6 => /lib/libc.so.6 (0x4008c000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
How is it possible, that gcc tries to link her internal libs into
binaries built?
Can anyone tell me, what I'm missing?
Thanks in advance
Frank
More information about the Gcc-help
mailing list