Is this right?

[grooveman]

I did a recent install from the 2007.0 disk, and downloaded the latest corresponding stage3 tarball (x86 for both).

When I untarred it, the make.conf contained this line:
CHOST="i486-pc-linux-gnu"

I always remember this being:
CHOST="i686-pc-linux-gnu"

but it has been a while... so... is 486 correct here? Or should I change it?

(this is a c3-2 nehemiah machine, if that makes a difference...)
_________________
To look without without looking within is like looking without without looking at all.

[Ehnvis]

You should change it to i686
_________________
HP NC 4010, Pentium-M 725 1.6GHz w/ 1Gb RAM, 60Gb Hitachi Travelstar.
Running Gentoo-2.6.21-r4 (again as 2.6.22 kernels hogs CPU), all but SD reader works fine.

[grooveman]

Is this a bug then? Should I report this?
_________________
To look without without looking within is like looking without without looking at all.

[grooveman]

Not so sure now... some things would not compile with i686... putting it back to 486 made it work...

There was no /usr/bin/i686-pc-linux-gnu

but there was a /usr/bin/i486-pc-linux-gnu

Looked like that was what portage was complaining about...
_________________
To look without without looking within is like looking without without looking at all.

[nikaya]

You've downloaded the wrong tarball.You need stage3-i686-2007.0.tar.bz2 and NOT stage3-x86-2007.0.tar.bz2.
Don't change the CHOST,download the correct stage3 tarball.
_________________
Notes on Dhamma
How to waste your time: look for an explanation of consciousness, ask to know what feeling is. (Nanavira Thera)

[grooveman]

[grooveman]

[nikaya]

[Nicias]

if you have already invest substantial work in your machine, and you don't want to redo it. you can change the CHOST.

Here is basically what it entails.

You do something like

emerge -1 linux-headers glibc binutils-config binutils gcc-config gcc

(maybe do this twice)

And hopefully that will work.

Then you do

emerge -e system

(maybe twice)

and then you do

emerge -e world

(maybe twice)

This *should* work, but it won't.

There are a few packages that behave badly when it comes to CHOST. For me they were xorg-x11 (these was before modular X) and python. These will stop working when you change your CHOST, as they are needed to build some things (like X I believe) some of your emerge's above will fail with cryptic errors. You can then emerge the required packaged and it should work itself out.

So what I think I did was

emerge -1 linux-headers glibc binutils-config binutils gcc-config gcc

(maybe I did this twice)
then I did what was done here
then I did

emerge -e system
emerge -e system
emerge -e world
emerge -e world

See more discussion in this post.

I didn't notice that I had done the same thing until about 6 months into using my machine and didn't want to have to redo that much work. If I had noticed within a week or so, I might have just reinstalled.

[grooveman]

Hey, thank you!
_________________
To look without without looking within is like looking without without looking at all.