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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



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.

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux