First:
- what is your current compiler
- what gcc-config do you have installed
- what profile do you use
- which USE-flags for gcc do you use


On 26-05-2008 22:55:08 +0200, Stefan Hoelldampf wrote:
> Hi,
> 
> I'm not able to emerge gcc-4.2.3 on amd64-linux (on RHEL4). It
> fails both during a bootstrap process and when re-emerging within an
> already existing installation. The problem seems to be located somewhere
> in the multilib area:
> 
> The gcc-4.2.3/libstdc++v3/configure script, called within
> build/x86_64-pc-linux-gnu/32/libstdc++-v3, is setting "gcc_no_link" in
> line 2664 depending on the result of:
> 
> > configure:2664: $EPREFIX/var/tmp/portage/sys-devel/gcc-4.2.3/work/build/./gcc/xgcc -B$EPREFIX/var/tmp/portage/sys-devel/gcc-4.2.3/work/build/./gcc/ -B$EPREFIX/usr/x86_64-pc-linux-gnu/bin/ -B$EPREFIX/usr/x86_64-pc-linux-gnu/lib/ -isystem $EPREFIX/usr/x86_64-pc-linux-gnu/include -isystem $EPREFIX/usr/x86_64-pc-linux-gnu/sys-include  -m32 -o conftest    conftest.c  >&5
> 
> Unfortunately, this fails with:
> 
> > $EPREFIX/usr/x86_64-pc-linux-gnu/bin/ld: skipping incompatible $EPREFIX/var/tmp/portage/sys-devel/gcc-4.2.3/work/build/./gcc/libgcc.a when searching for -lgcc
> > $EPREFIX/usr/x86_64-pc-linux-gnu/bin/ld: cannot find -lgcc
> > collect2: ld returned 1 exit status
> > configure:2667: $? = 1
> 
> Due to this failed run, "gcc_no_link" is set to "yes".
> 
> It's obvious that work/build/gcc/libgcc.a is incompatible due to 64bit,
> but work/build/gcc/32/libgcc.a has been created.
> 
> 
> Later on,
> > checking for ld that supports -Wl,--gc-sections...
> fails with
> > configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> due to "gcc_no_link" set to "yes".
> 
> 
> Any hints are appreciated!
> 
> 
> Best regards,
> 	Stefan
> 
> -- 
> gentoo-alt@g.o mailing list
> 

-- 
Fabian Groffen
Gentoo on a different level
-- 
gentoo-alt@g.o mailing list