[arch-general] [arch-dev-public] The need for /lib64 - testing please

[Thomas Bächler]

Am 01.07.2011 12:16, schrieb Emmanuel Benisty:
>> The problem is quite simple: The ELF binary hardcodes the path to the
>> interpreter (which is the linker). Binaries that were compiled for other
>> distributions or generic binaries distributed by third parties will have
>> the path "/lib64/ld-linux-x86-64.so.2" hardcoded as their interpreter -
>> I don't know where this convention comes from and why they didn't choose
>> /lib (choosing /lib would be no problem, as the file names for the 32
>> and 64 bit linkers differ, the former is ld-linux.so.2).
> 
> Just FTR, it most likely comes from
> http://www.pathname.com/fhs/pub/fhs-2.3.html#LIB64

I am pretty sure this came after the first distributor chose this
convention for AMD64.

Anyway, the reasons for the choice are explained there.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20110701/618a4280/attachment.asc>