| 1 |
Hi Ulrich, |
| 2 |
|
| 3 |
On 2020/11/09 12:59, Ulrich Mueller wrote: |
| 4 |
>>>>>> On Mon, 09 Nov 2020, Jaco Kroon wrote: |
| 5 |
>> What is the actual "target" objective with the change? I would have |
| 6 |
>> expected (not being one to follow this too closely): |
| 7 |
>> lib/ - arch independent stuff (eg, netifrc / dhclient etc scripts). |
| 8 |
>> lib32/ - 32-bit specific stuff (libs for 32-bit). |
| 9 |
>> lib64/ - 64-bit specific stuff (libs for 64-bit). |
| 10 |
> It is explained here: |
| 11 |
> https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout#Rationale |
| 12 |
|
| 13 |
Thank you, that makes a lot of sense and answers all my questions |
| 14 |
...just wondering where the lib32 => lib symlink comes from now. |
| 15 |
|
| 16 |
So if anybody else ends up wondering: |
| 17 |
|
| 18 |
jkroon@plastiekpoot ~ $ ls -lah /lib32 /usr/lib32 /usr/local/lib32 |
| 19 |
ls: cannot access '/usr/local/lib32': No such file or directory |
| 20 |
lrwxrwxrwx 1 root root 3 Nov 9 10:02 /lib32 -> lib |
| 21 |
lrwxrwxrwx 1 root root 3 Nov 9 10:02 /usr/lib32 -> lib |
| 22 |
|
| 23 |
equery has some answers that there are still stuff installed into |
| 24 |
/usr/lib32 (which will likely clear over time, and the symlink will be |
| 25 |
unmerged). There is this one potential pitfall down the line that I'm |
| 26 |
seeing, fairly certain this would have been covered and that a remerge |
| 27 |
of glibc will fix this: |
| 28 |
|
| 29 |
jkroon@plastiekpoot ~ $ equery belongs /lib32 /usr/lib32 |
| 30 |
... |
| 31 |
sys-libs/glibc-2.32-r2 (/lib -> lib64) |
| 32 |
|
| 33 |
So job well done to the implementation team!! Great work thank you! |
| 34 |
|
| 35 |
Kind Regards, |
| 36 |
Jaco |
Archives