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