hmm, there have been a number of threads about updating old systems, but none with this problem.

By the looks of the error it is not portage but the build. You did use quotes for FEATURES="-sandbox" ... and it was only a typo in your post wasn't it?

Also in your emerge --info it is still showing old python and bash versions,... did you

Code:

env-update
source /etc/profile

after the changes?

I would try upgrading some of the toolchain pkgs first, like binutils which is a much needed one for gcc._________________Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

I finally figured out from another forum that binutils needed updated also. So I manually updated that using the same directions from the blog. Only they left out that I needed to eselect the new binutils.

The 3 packages you want emerged to kick things off are glibc, binutils & gcc. Your message above spells binutils.If you can't emerge that, you do have a problem. need to again emerge a re-emerged binary._________________idella4@aus

I did run python-updater also. I am now in the process of getting all the required packages updated via emerge now that its working. gcc, glibc, binutils, bash and portage for the ones I am working no now. I hope after those get updated I can update the rest all at once.

I doubt it, there have been a few upgrade snags your likely to run across depending on the pkgs installed.

Don't forget to add the --keep-going option to the emerge command. It'll help get past failed merges, give you a list of failed ones at the end. Often they will merge the second time around (often due to mis-calculating the merge order, so deps are properly satisfied the second time)._________________Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

I've been watching this thread out of interest, since two years ago I tried this with a box that hadn't been updated in 6 months. I'm amazed you got anywhere, mine stopped emerging for I forgot what reason after a couple hours working at it. I didn't even try to find a solution, at that point I decided that everything was telling me to install fresh.

I had to revert back to the snapshot before I started updating. I am going to grab a snapshot after each update so if one breaks it like coreutils did I can revert back. I am going to modify my strategy a little. While I was trying to update everything and then the kernel I think I will try to update the bare minimum then the kernel. I dont know how much I will be able to get updated without updating coreutils.

* This profile is merely a convenience for people who require a more
* minimal profile, yet are unable to use hardened due to restrictions in
* the software being used on the server. This profile should also be used
* if you require GCC 4.1 or Glibc 2.4 support. If you don't know if this
* applies to you, then it doesn't and you should probably be using
* Hardened, instead.

manually and it works. Seems like portage fails at it for some unknown reason though. Any ideas what portage could suddenly mess up?_________________Leader and Head Programmer: Epsylon, Drag[en]gine and others

Somebody mentioned something about udev having troubles with older kernels. That machine still has 2.6.19 running. Could this have an influence?_________________Leader and Head Programmer: Epsylon, Drag[en]gine and others

Bumping up the kernel fixes the problem. Seems to be incompatibility with old kernels. God had this been "the hate" hunting down all the symbols that moved around (broken NAT on a router server SUCKS! :/ ... especially if it takes like 5 recompiles to find all the illogical stray symbols)._________________Leader and Head Programmer: Epsylon, Drag[en]gine and others

I can't seem to understand why people neglect kernel versions on such updates.
I think that the right path is portage->glibc->binutils->gcc->portage->glibc->binutils->kernel+header->reboot->rest_________________Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball

I can't seem to understand why people neglect kernel versions on such updates.
I think that the right path is portage->glibc->binutils->gcc->portage->glibc->binutils->kernel+header->reboot->rest

Do this over SSH and then see how you swear if the kernel doesn't come up after reset while the server is literally "in another state"._________________Leader and Head Programmer: Epsylon, Drag[en]gine and others