On Tuesday 26 September 2006 12:20, Duncan wrote: > Other packages that likely won't compile will be glibc and gcc, since > they both have 32-bit aspects as well, and that's what's horked.
Nope, they both compile just fine. Of those, only sandbox is causing me grief. > ... the majority of the packages will be 64-bit, so lack of a > valid 32-bit compiler setting won't affect them at all. Only the > toolchain packages, for the most part, will be affected, so sandbox, > glibc, gcc, and maybe binutils. Actually, only sandbox and module-init-tools are failing. > if you are lucky, simply setting the 32-bit compiler will put you back in > good form. I can't see why selecting a 32-bit compiler should make portage work again. Surely I need a 64-bit compiler for almost the whole system? I haven't changed any multilib flags, so I should still have both, no? For the moment I'm continuing with emerge -e world, just skipping the few packages that fail (just the two of them so far) - they still exist, after all, in their earlier state. > ... I wonder how much of your earlier problems might have the same > thing? Oh, well, hindsight's always 20/20, as they say. One more thing > to add to our list of things to check... > > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman -- Rgds Peter -- [email protected] mailing list
