| 1 |
Dnia 11 grudnia 2017 08:25:22 CET, Xavier Miller <xaviermiller@g.o> napisał(a): |
| 2 |
>Le 2017-12-10 23:24, Michał Górny a écrit : |
| 3 |
>> I suspect you mean python-exec scripts, because Python modules still |
| 4 |
>> land in /usr/lib64. In which case, everything's fine. |
| 5 |
> |
| 6 |
>Could be. |
| 7 |
> |
| 8 |
>Glad to hear the migration is OK. |
| 9 |
> |
| 10 |
>My systems are migrated, and stable. |
| 11 |
> |
| 12 |
>Just a last dummy question : why is lib64 migrated to lib64 and lib32 |
| 13 |
>to |
| 14 |
>lib, and not the reverse? |
| 15 |
>We have /lib and /lib64 that were before merged, and /lib32 that was an |
| 16 |
> |
| 17 |
>exception and prone to disapear the day blobs will decide to finally go |
| 18 |
> |
| 19 |
>64 bits. |
| 20 |
|
| 21 |
It's because x86 (32-bit) ABI specifies that libraries are located in lib, and x86_64 ABI uses lib64. We've so far had to hack some stuff (binutils notably) to support lib32. |
| 22 |
|
| 23 |
> |
| 24 |
>Anyway, thank you for the job done! |
| 25 |
> |
| 26 |
>Xavier. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny (by phone) |
Archives