| 1 |
On 6/28/06, Darren Grant <dgrant@×××××××××××.ca> wrote: |
| 2 |
> Any chance that's what's causing my gcc problems now? |
| 3 |
|
| 4 |
Hmm, I doubt it. But in comparing what you have posted to my AMD64 |
| 5 |
box, I see some things that don't look right. For example, on my |
| 6 |
AMD64 box, I have: |
| 7 |
|
| 8 |
Gentoo Base System version 1.12.0 |
| 9 |
Portage 2.1 (default-linux/amd64/2006.0, gcc-4.1.1/amd64-vanilla, |
| 10 |
glibc-2.4-r3, 2.6.16 x86_64) |
| 11 |
================================================================= |
| 12 |
System uname: 2.6.16 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ |
| 13 |
|
| 14 |
Notice my profile is default-linux/amd64/<something>, where you have |
| 15 |
your profile as just default-linux/amd64. I'm not sure that is |
| 16 |
actually supported...and may in fact be the cause of your trouble. |
| 17 |
|
| 18 |
The new profiles (starting with 2005.1) are "multilib" by default, so |
| 19 |
for example merging glibc will try to build both i686 and x86_64 |
| 20 |
versions. So it is in fact perfectly reasonble for an emerge of glibc |
| 21 |
to try to build a i686 version, but *only* if you are using a multilib |
| 22 |
profile. Similarly gcc would try to build i686 versions of its |
| 23 |
libraries, but would require an i686 glibc to be available first. |
| 24 |
|
| 25 |
I suspect what you need to do is: |
| 26 |
|
| 27 |
cd /etc |
| 28 |
rm make.profile |
| 29 |
ln -s ../usr/portage/profiles/default-linux/amd64/2005.1/no-multilib |
| 30 |
|
| 31 |
Then try re-merging glibc and gcc. |
| 32 |
|
| 33 |
If you want to switch to the multilib profile, the symlink should be |
| 34 |
to /usr/portage/profiles/default-linux/amd64/2005.1 or 2006.0. But |
| 35 |
you might want to ask on gentoo-amd64 about how to switch from |
| 36 |
no-multilib to a multilib profile... |
| 37 |
|
| 38 |
-Richard |
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives