On Sat, Mar 26, 2011 at 1:36 PM, Bill Longman <bill.long...@gmail.com> wrote: > On Sat, Mar 26, 2011 at 12:56 PM, Mark Knecht <markkne...@gmail.com> wrote: <SNIP> >> I had nothing linked to libmpfr.so.1 so that wasn't the root cause/ >> >> In my case it seems to be driven by bugs like this: >> >> http://bugs.gentoo.org/show_bug.cgi?id=360425 >> >> Seems the only thing to do it just wait for devs to fix it. (And >> wonder why something like python-2.7 gets released as stable with >> stuff like this hanging about....) >> >> Cheers, >> Mark >> > > The libmpfr change bit me on one of my amd64 machines. I did the > revdep-rebuild on the library and then gcc was broken. I recompiled > everything but still sandbox and gcc won't compile. > -- > Bill Longman >
Bill, I got bit by the sandbox/gcc problem yesterday. In my case, on a machine with a KDE profile && after reviewing Gentoo bug reports, I did the following: eselect profile set 1 cd /lib ln -s ../lib32/ld-linux.so.2 . emerge sandbox emerge --sync emerge glibc emerge @preserved-rebuild eselect profile set 4 emerge -e -j9 @system and an hour later I was back to functional without those messages about not being able to build C programs, etc. I don't suggest ANY of that is understood by the likes of me but it did seem to solve the problem which was (apparently) wrapped around some sort of missing link which allows 64-bit machines to run 32-bit programs. (Or that's about all I could get out of what I read....) Hope this helps, and hoping someone more knowledgable than I chimes in with what I should have/could have done to do this more easily. Cheers, Mark
