1 |
On Sat, Mar 26, 2011 at 1:36 PM, Bill Longman <bill.longman@×××××.com> wrote: |
2 |
> On Sat, Mar 26, 2011 at 12:56 PM, Mark Knecht <markknecht@×××××.com> wrote: |
3 |
<SNIP> |
4 |
>> I had nothing linked to libmpfr.so.1 so that wasn't the root cause/ |
5 |
>> |
6 |
>> In my case it seems to be driven by bugs like this: |
7 |
>> |
8 |
>> http://bugs.gentoo.org/show_bug.cgi?id=360425 |
9 |
>> |
10 |
>> Seems the only thing to do it just wait for devs to fix it. (And |
11 |
>> wonder why something like python-2.7 gets released as stable with |
12 |
>> stuff like this hanging about....) |
13 |
>> |
14 |
>> Cheers, |
15 |
>> Mark |
16 |
>> |
17 |
> |
18 |
> The libmpfr change bit me on one of my amd64 machines. I did the |
19 |
> revdep-rebuild on the library and then gcc was broken. I recompiled |
20 |
> everything but still sandbox and gcc won't compile. |
21 |
> -- |
22 |
> Bill Longman |
23 |
> |
24 |
|
25 |
Bill, |
26 |
I got bit by the sandbox/gcc problem yesterday. In my case, on a |
27 |
machine with a KDE profile && after reviewing Gentoo bug reports, I |
28 |
did the following: |
29 |
|
30 |
eselect profile set 1 |
31 |
cd /lib |
32 |
ln -s ../lib32/ld-linux.so.2 . |
33 |
emerge sandbox |
34 |
emerge --sync |
35 |
emerge glibc |
36 |
emerge @preserved-rebuild |
37 |
eselect profile set 4 |
38 |
emerge -e -j9 @system |
39 |
|
40 |
and an hour later I was back to functional without those messages |
41 |
about not being able to build C programs, etc. |
42 |
|
43 |
I don't suggest ANY of that is understood by the likes of me but it |
44 |
did seem to solve the problem which was (apparently) wrapped around |
45 |
some sort of missing link which allows 64-bit machines to run 32-bit |
46 |
programs. (Or that's about all I could get out of what I read....) |
47 |
|
48 |
Hope this helps, and hoping someone more knowledgable than I chimes in |
49 |
with what I should have/could have done to do this more easily. |
50 |
|
51 |
Cheers, |
52 |
Mark |