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