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