Re: [PATCH] aarch64: use lib64 as default lib and slib directory

[Marcus Shawcroft <marcus.shawcroft@gmail.com>]

The patches applied to gcc and glibc to move aarch64 libraries from
/lib to /lib64 are inconsistent.  We are now in a situation where gcc
expects the dynamic loader to be /lib while glibc installs it to
/lib64.  I don't see a trivial change to Andreas' glibc patch.  I
think these patches need to be reverted until a working solution is
found.

/Marcus

On 14 March 2013 15:11, Carlos O'Donell <carlos@redhat.com> wrote:
> On 03/14/2013 04:46 AM, Marcus Shawcroft wrote:
>> On 13 March 2013 16:29, Joseph S. Myers <joseph@codesourcery.com> wrote:
>>> On Wed, 13 Mar 2013, Jakub Jelinek wrote:
>>>
>>>>> However, there was some recent discussion about this in gcc.
>>>>>
>>>>> Jakub, What's the status?
>>>>
>>>> No progress there, see the
>>>> http://gcc.gnu.org/ml/gcc-patches/2013-03/msg00288.html
>>>> thread.  I'd really like to get it resolved before we cut
>>>> GCC 4.8.0-rc1 this week.
>>>
>>> If it does change to /lib64, it would seem odd for the dynamic linker path
>>> (GLIBC_DYNAMIC_LINKER in aarch64-linux.) to stay as
>>> /lib/ld-linux-aarch64.so.1 rather than also being in /lib64 (although s390
>>> also puts the 64-bit dynamic link in /lib).
>>
>> Changing the location of the linker breaks binaries. I'm not convinced
>> the disruption associated with that is justified.
>
> I agree with Marcus. If we don't need to move the dynamic linker then
> we shouldn't.
>
> Cheers,
> Carlos.
>