1 |
On 10/09/2014 04:50, Joseph wrote: |
2 |
> On 09/10/14 04:27, Kerin Millar wrote: |
3 |
>> On 10/09/2014 04:21, Joseph wrote: |
4 |
>>> On 09/10/14 03:59, Kerin Millar wrote: |
5 |
>>>> On 09/09/2014 19:36, Joseph wrote: |
6 |
>>> [snip] |
7 |
>>> |
8 |
>>>>> |
9 |
>>>>> Running on my other system I get: |
10 |
>>>>> equery b libstdc++.so.6 |
11 |
>>>>> * Searching for libstdc++.so.6 ... sys-devel/gcc-4.5.4 |
12 |
>>>>> (/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 -> |
13 |
>>>>> libstdc++.so.6.0.14) |
14 |
>>>>> |
15 |
>>>>> env-update - doesn't work either |
16 |
>>>>> |
17 |
>>>> |
18 |
>>>> Check beneath /etc/env.d/ld.so.conf.d and ensure that there is a file |
19 |
>>>> defining the appropriate paths for your current version of gcc. Here's |
20 |
>>>> how it looks on my system: |
21 |
>>>> |
22 |
>>>> # cd /etc/ld.so.conf.d |
23 |
>>>> # ls |
24 |
>>>> 05binutils.conf 05gcc-x86_64-pc-linux-gnu.conf |
25 |
>>>> # cat 05gcc-x86_64-pc-linux-gnu.conf |
26 |
>>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32 |
27 |
>>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3 |
28 |
>>>> |
29 |
>>>> Once you have made any necessary changes, run ldconfig. |
30 |
>>>> |
31 |
>>>> --Kerin |
32 |
>>> |
33 |
>>> Thanks Kerin, for the pointer. |
34 |
>>> I think I have a bigger problem, and don't know how to fix it. |
35 |
>>> |
36 |
>>> Yes, I have the same file /etc/ld.so.conf.d |
37 |
>>> # ls # 05gcc-x86_64-pc-linux-gnu.conf |
38 |
>>> # cat /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32 |
39 |
>>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3 |
40 |
>>> |
41 |
>>> However, those directories are empty (only one file): |
42 |
>>> # ls -al /usr/lib/ |
43 |
>>> libbrcomplpr2.so |
44 |
>> |
45 |
>> Is /usr/lib an actual directory or a symlink? Assuming that you use a |
46 |
>> stock amd64 (multilib) profile, it should be a symlink to lib64. If you |
47 |
>> find that it is a directory and that you also have a lib64 directory, |
48 |
>> try the commands below. You can skip the busybox and exit commands if |
49 |
>> you are doing this in a chroot rather than on a live system. |
50 |
>> |
51 |
>> # busybox sh |
52 |
>> # cd /usr/ |
53 |
>> # mv lib lib.old |
54 |
>> # ln -s lib64 lib |
55 |
>> # exit |
56 |
>> |
57 |
>>> On my other working system this directory "/usr/lib/" contain about 2020 |
58 |
>>> files. |
59 |
>>> What had happened? |
60 |
>>> After emerging some files and system I was running command: fstrim -v / |
61 |
>>> (as the disk is SSD). |
62 |
>>> Could it have something to do with the fact that these directories are |
63 |
>>> empty? |
64 |
>> |
65 |
>> No. Using fstrim does not delete files. |
66 |
>> |
67 |
>> --Kerin |
68 |
> |
69 |
> Kerin you are a magician! THANK YOU!!! |
70 |
> Yes, it worked. Everything is back to normal. |
71 |
> |
72 |
> I can still not comprehend what had happened :-/ why all of a sudden in |
73 |
> the middle of compilation it all vanished. |
74 |
|
75 |
Were you doing anything outside of portage that may have had a hand in it? |
76 |
|
77 |
Incidentally, you should move libbrcomplpr2.so to /usr/lib32. Some |
78 |
googling suggests to me that it is a library included in a proprietary |
79 |
Brother printer driver package. You can use the file command to confirm |
80 |
that it is a 32-bit library. |
81 |
|
82 |
--Kerin |