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