Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-alt
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-alt@g.o
From: Fabian Groffen <grobian@g.o>
Subject: Re: Emerging gcc-4.2.3 fails on amd64-linux
Date: Fri, 20 Jun 2008 21:43:31 +0200
On 04-06-2008 21:17:49 +0200, Stefan Hoelldampf wrote:
> Fabian Groffen wrote:
> 
> > 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.
> 
> I have finally found the problem. The error is caused by
> no-libs-for-startfile.patch due to the multilib part of gcc.
> https://bugs.gentoo.org/show_bug.cgi?id=224931 has a patch for
> sys-devel/gcc-{4.2.3,4.2.4,4.3.0}.

I think this is resolved currently by the elimination of the multilib
profile.  amd64-linux has been converted to a true 64-bits profile now,
which is reported to make this bug go away.


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


References:
Emerging gcc-4.2.3 fails on amd64-linux
-- Stefan Hoelldampf
Re: Emerging gcc-4.2.3 fails on amd64-linux
-- Fabian Groffen
Re: Emerging gcc-4.2.3 fails on amd64-linux
-- Stefan Hoelldampf
Re: Emerging gcc-4.2.3 fails on amd64-linux
-- Fabian Groffen
Re: Emerging gcc-4.2.3 fails on amd64-linux
-- Stefan Hoelldampf
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Emerging gcc-4.2.3 fails on amd64-linux
Next by thread:
Re: [PREFIX] Problem compiling libperl on Solaris 11
Previous by date:
Re: octave/gnuplot on OSX, no aquaterm!
Next by date:
[Q] What's causing python on Opensolaris to fail to import modules?


Updated Jun 17, 2009

Summary: Archive of the gentoo-alt mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.