C compiler cannot create executables

cornice

I know that questions similar to this have been posted but I'm wondering if there might be a better solution than reinstalling. Here's what happened.

First I ran a stable system with #accept_keywords="~x86". Then after an update something broke and in an act of desperation switched to accept_keywords="~x86" and upgraded some packages. I never did an emerge -u world so I figured that pretty soon the stable packages would catch up to me and I would switch back to #accept_keywords="~x86". That never seemed to happen and I ended up with more and more unstable packages just to stay ahead of the security fixes. Then I started to have troubles with some updates. More of the unstable ebuilds were failing to compile. Since the system in question is rather important to me I figured I should return to a more stable position of #accept_keywords="~x86".

I think you can guess the rest.

Any thoughts on what I can do to get out of this without starting over? Some programs work fine and some do not so I think I have one version of libC and GCC compiled for something else. It seems as though the programs that work were compiled a while ago and the ones that don't were recent unstable compiles.

Any help would be greatly appreciated. After searching the forums database I have found that people with slightly similar problems fixed this by copying the /usr dirctory from the stage 3 CD while others simply started over. I would like to find a better solution if possible but I suppose a reinstall isn't so bad. At least it's Gentoo. ;-)

Cheers,

Scott

Pythonhead

cornice · Posted: Mon Jun 16, 2003 10:25 am Post subject:

GCC = 3.2.2
GLibC = 2.3.1-r4

I get a lot of messages like this:

libpthread.so.0: version 'GLIBC_2.3.2' not found

I'm wondering if there is a way to copy the necessary files to get GCC working (either manually or with a binary ebuild) and then do an emerge -e world. I just don't know exactly where to start when copying files. I have a stage 3 tarball and another gentoo system running 3.2.2-r2 and 2.3.2-r1 to copy from though.

I guess I can do a make install on the other box and watch what goes where and then copy by hand from the stage 3 tarball. Then again I'm not sure what might break in the middle of that process if anything. I suppose booting from CD would be wise. :wink:

Any thoughts?

Thanks!

Pythonhead · Posted: Mon Jun 16, 2003 11:25 pm Post subject:

I don't know of any easy way to fix your problem. I see a lot of these messages, where people blindly update world and screw up their gcc/glibc. Maybe portage should PRINT A BIG WARNING on gcc/glibc upgrades, or not let people do it with emerge world.

Anyways, I think you're stuck at re-emerging everything you emerged during your ~x86 period, i.e. anything that gives this type of message:

cornice · Posted: Tue Jun 17, 2003 2:04 am Post subject:

Genone · Posted: Tue Jun 17, 2003 9:57 am Post subject:

A tip for future experiments like this: put buildpkg in your FEATURES varaible in make.conf or use the -b option for emerge. That way you generate binary packages of all installed programs, they can really help in such situations.

cornice · Posted: Tue Jun 17, 2003 11:07 am Post subject: