From: Jakub Jelinek <jakub@redhat.com>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: Michael Hope <michael.hope@linaro.org>,
cross-distro@lists.linaro.org,
Adam Conrad <adconrad@debian.org>,
linaro-toolchain@lists.linaro.org,
Steve McIntyre <steve.mcintyre@linaro.org>,
Jeff Law <law@redhat.com>,
gcc-patches@gcc.gnu.org, libc-ports@sourceware.org
Subject: Re: Phone call (was Re: Armhf dynamic linker path)
Date: Thu, 12 Apr 2012 07:48:00 -0000 [thread overview]
Message-ID: <20120412074729.GJ16117@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <CAAqcGHmJL4jiL8u3MMqw_B38m1HHbVGdZouiEqJV3o_JkLPf5g@mail.gmail.com>
On Thu, Apr 12, 2012 at 10:33:08AM +0300, Riku Voipio wrote:
> On 12 April 2012 09:05, Jakub Jelinek <jakub@redhat.com> wrote:
> > 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 some value of consistency. x86_64, mips64, powerpc64 and sparc64
> install to /lib64. But on ia64 it is /lib/ld-linux-ia64.so.2 and on
ia64 installs in /lib, because it isn't a multilibbed architecture.
> s390x it is /lib/ld64.so.1 [1].
Ok, I forgot about this, I've tried to convince s390x folks to move it
to /lib64/ld64.so.1 many years ago, but that just didn't happen, so
/lib/ld64.so.1 is just a symlink to /lib64/ld64.so.1.
Upstream glibc binaries use /lib64/ld64.so.1 as their dynamic linker,
while all other packages use /lib/ld64.so.1 as that is hardcoded in gcc.
That is an argument that perhaps /lib/ld-linux-armhf.so.3 could be
acceptable too, as it would follow the s390x model, I wouldn't be terribly
happy about that, but I could live with that.
Jakub
next prev parent reply other threads:[~2012-04-12 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120331103406.GA17776@einval.com>
[not found] ` <201204100019.13472.vapier@gentoo.org>
[not found] ` <4F83B5AD.3010302@redhat.com>
[not found] ` <201204100033.08853.vapier@gentoo.org>
[not found] ` <4F83B939.10205@redhat.com>
[not found] ` <4F84AC96.6020500@redhat.com>
[not found] ` <20120411010608.GC25263@einval.com>
[not found] ` <20120411223755.GD25263@einval.com>
2012-04-11 23:22 ` Michael Hope
[not found] ` <CAHAq8pGbEtmu=QuOFGJpPCck6fFmb63Zm+Ax5B9Bg-m3U1UQ_w@mail.gmail.com>
2012-04-12 0:16 ` Michael Hope
2012-04-12 1:15 ` Paulo César Pereira de Andrade
2012-04-12 1:40 ` Michael Hope
2012-04-12 2:15 ` Paulo César Pereira de Andrade
[not found] ` <20120412003801.GS26898@dream.aleph1.co.uk>
2012-04-12 1:27 ` Michael Hope
2012-04-12 6:06 ` Jakub Jelinek
[not found] ` <CAAqcGHmJL4jiL8u3MMqw_B38m1HHbVGdZouiEqJV3o_JkLPf5g@mail.gmail.com>
2012-04-12 7:48 ` Jakub Jelinek [this message]
2012-04-12 17:48 ` Mike Frysinger
2012-04-12 17:53 ` Jakub Jelinek
2012-04-12 18:14 ` Mike Frysinger
2012-04-12 17:46 ` Mike Frysinger
2012-04-12 20:33 ` Paulo César Pereira de Andrade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120412074729.GJ16117@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=adconrad@debian.org \
--cc=cross-distro@lists.linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=libc-ports@sourceware.org \
--cc=linaro-toolchain@lists.linaro.org \
--cc=michael.hope@linaro.org \
--cc=riku.voipio@linaro.org \
--cc=steve.mcintyre@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).