On 6/28/06, Darren Grant <[EMAIL PROTECTED]> wrote:
Any chance that's what's causing my gcc problems now?
Hmm, I doubt it. But in comparing what you have posted to my AMD64 box, I see some things that don't look right. For example, on my AMD64 box, I have: Gentoo Base System version 1.12.0 Portage 2.1 (default-linux/amd64/2006.0, gcc-4.1.1/amd64-vanilla, glibc-2.4-r3, 2.6.16 x86_64) ================================================================= System uname: 2.6.16 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ Notice my profile is default-linux/amd64/<something>, where you have your profile as just default-linux/amd64. I'm not sure that is actually supported...and may in fact be the cause of your trouble. The new profiles (starting with 2005.1) are "multilib" by default, so for example merging glibc will try to build both i686 and x86_64 versions. So it is in fact perfectly reasonble for an emerge of glibc to try to build a i686 version, but *only* if you are using a multilib profile. Similarly gcc would try to build i686 versions of its libraries, but would require an i686 glibc to be available first. I suspect what you need to do is: cd /etc rm make.profile ln -s ../usr/portage/profiles/default-linux/amd64/2005.1/no-multilib Then try re-merging glibc and gcc. If you want to switch to the multilib profile, the symlink should be to /usr/portage/profiles/default-linux/amd64/2005.1 or 2006.0. But you might want to ask on gentoo-amd64 about how to switch from no-multilib to a multilib profile... -Richard -- gentoo-user@gentoo.org mailing list
