Duncan wrote: > But what what's much more likely to be happening is that your portage is > too old to work with a newer tree and/or the newer profile the new > machine is on. That's particularly true if you were on stable, not > > It's also possible that the linked glibc or other (libstdc++ for C++ > apps, ABI affecting CFLAGS such as -mregparm=X) is too different.
I tried to recover using a Gentoo universal CD, but it was too much work. I ended-up reinstalling from a stage3, untarred a recent portage snapshot and emerged the binpkg from the Athlon64 X2 system. I first emerged portage, then system, then added the world stuff. I haven't finished yet, I needed some packages not available on the main system, so no GUI yet. For the packages (e.g. seamonkey) I need to recompile I try to use the --buildpkgonly emerge option on the main system to generate a binpkg, rather than setting up the distcc environment, looks easier. raf
