This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] ARM: Use different linker path for hardfloat ABI
On 4 April 2012 04:17, Andrew Haley <firstname.lastname@example.org> wrote:
> On 04/03/2012 05:09 PM, Richard Earnshaw wrote:
>> On 03/04/12 12:01, Jakub Jelinek wrote:
>>> On Tue, Apr 03, 2012 at 11:45:30AM +0100, Richard Earnshaw wrote:
>>>> If, so then there's only one way to sort out this mess.
>>>> /lib/arm-linux-gnueabi/ld-linux.so.3 ?Location of soft-float loader
>>>> /lib/arm-linux-gnueabihf/ld-linux.so.3 Location of hard-float loader
>>> The above scheme is a Debianism which no other distro is using.
>>> ? ? ?Jakub
>> Not really, it's just a naming convention for where the config-specific
>> dynamic loader lives. ?It doesn't affect where the remaining shared
>> libraries live.
>> The subdirectories could be called fred and jim and it would still work.
>> ?The only thing required is that this part of the naming scheme be
>> agreed amongst the distros.
>> This looks to me like it's turning into a bike-shed painting excerise
>> between the distros out there. ?That's really sad.
> I don't think we ever even had the discussion: Debian invented their
> Debian-internal scheme for managing multiple ABIs. ?They have in the past
> used patched versions of gcc, as in the case of x86_64.
(cc'ed cross-distro as the discussion is also going on there. This
patch continues that)
I like the idea of incompatible binaries having different loaders.
The path doesn't matter but the concept does. Like i686/x86_64, it
gives distros the option to install different binaries alongside each
other for compatibility, performance, or upgrade reasons. The
compatibility cost is nice and low and lets Debian do some interesting
cross development things.
No one has released a hard float based distro yet. We have time to
discuss and fix this so we don't get in the crazy situation where a
third party binary only runs on some distros.