On Tue, May 27, 2008 14:30, Fabian Groffen wrote:
>> $ rpm -qf /usr/bin/gcc
>> gcc-3.4.6-9 # RHEL4 system compiler
>
> I assume RHEL is a multilib system, is it?
Right, RHEL4 x86_64 is a multilib system.
>> $ emerge -p gcc-config
>> [ebuild R ] sys-devel/gcc-config-1.4.0-r04.3
>
> Can you list ${EPREFIX}/lib/libgcc_s* please?
$ ls -1 $EPREFIX/lib/libgcc_s.so*
$EPREFIX/lib/libgcc_s.so
$EPREFIX/lib/libgcc_s.so.1
$ file $EPREFIX/lib/libgcc_s.so*
$FILE/lib/libgcc_s.so: ELF 32-bit LSB shared object, Intel 80386,
version 1 (SYSV), dynamically linked, stripped
$EPREFIX/lib/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386,
version 1 (SYSV), dynamically linked, stripped
> Multilib indeed seems to be the problem, but the question is why it
> finds the wrong lib. This can also be related to the linker (binutils)
> looking in wrong paths or something.
It does not seem to depend on the linker in $EPREFIX. Bootstrapping gcc
without emerging binutils lets it fail in the same way:
/usr/bin/ld: skipping incompatible
$EPREFIX/var/tmp/portage/sys-devel/gcc-4.2.3/work/build/./gcc/libgcc.a
when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
So the system linker /usr/bin/ld is used in this case.
Best regards,
Stefan
--
gentoo-alt@g.o mailing list
|
