Duncan wrote: > march=k8 (aka opteron, aka athlon64, aka athlon-fx) is supposed to be a > synonym, that is, identical to march=athlon64 (and the other akas > above). However, newer gcc versions also have march=k8-sse3, which will
That is interesting piece of information. Where did you get it? The gcc man page is not very informative, just listing the four names on the same row. > 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 > ~arch, as stable portage is already somewhat behind the latest features, > in addition to that year. In particular, if you have an old pre- > cascading profiles portage, it's stale indeed. If the old profile is > still around, perhaps you can update just portage, first. The old profile was 2007.0, I don't know if that was pre-cascading. The first problem I had was that portage snapshot is now compressed with lzma, which in the old system was not even installed. I managed to find a .tar.bz2 snapshot and tried to update portage as you suggest, but again was bitten by lzma (some packages ship in lzma compress format). The while trying to work around the fact that lzma was not compiling I made the linux-utils mess. > FWIW for the future, I'd suggest updating at least every six months or > so, just to keep from getting in such binds. But six-month updates are > already likely to be more difficult than necessary. Three-month updates > are the most I'd want to go on a routine basis. By a year out, indeed, > grabbing the latest stage tarball and going from there, as you discuss > below, is getting to be the most viable option. I was not so keen to frequent updates due to the long compilation time on the Sempron plus the fact that I do not have frequent access to that system. I just recently discovered the binpkg feature, I'm going to update the system more often now. > Another alternative, if you trust a specific Gentoo/amd64 user, is to ask > them to create a binpkg for you, specifying USE and CFLAGS as needed. That's not necessary, I do have other gentoo boxes working. raf
