Re: Phone call (was Re: Armhf dynamic linker path)

["Paulo César Pereira de Andrade" <paulo.cesar.pereira.de.andrade@gmail.com>]

Em 12 de abril de 2012 03:05, Jakub Jelinek <jakub@redhat.com> escreveu:
> On Thu, Apr 12, 2012 at 11:22:13AM +1200, Michael Hope wrote:
>> All good.  My vote is for /lib/ld-arm-linux-gnueabihf.so.3 as it:
>
> The directory should be /libhf/ or /libhfp/ for that for consistency
> with all the other architectures.  Note e.g. x86_64 dynamic linker
> is /lib64/ld-linux-x86-64.so.2, not /lib/ld-linux-x86-64.so.2.
> For distros that choose to multilib softfp vs. hardfp all the hardfp
> libraries would go into the usual */lib{qual} paths (for qual hf resp.
> hfp), for others /libhf can be a symlink to /lib or for those doing
> multiarch stuff can be a symlink to the multiarch location of the thing.

  I would feel a bit better with a commitment for multilib if using /libhf,
but really just to make users life easier. Providing the infrastructure
(by having multilib packages) is asking for it to be used. In the skype
example, if multilib is supported by all distros, skype may as well
provide only an armv5te software float build for linux arm.
  This is the reason, for example, to install skype in my x86_64
computer I need to install 32 bit qt, alsa, X11 libraries, etc to be
able to install x86 skype.

> I'm fine with arm and hf (resp. hfp) being mentioned in the name of
> the dynamic linker, but IMNSHO having there gnu and eabi strings
> is an overkill - why mention gnu there, when all the other
> architectures which also have GNU libc dynamic linkers don't?  That
> part is implicit.  And, EABI is implied by so.3, softfp dynamic linker
> for EABI is /lib/ld-linux.so.3 while softfp dynamic linker for the old
> ABI is /lib/ld-linux.so.2.
>
>        Jakub

Paulo