From: "Carlos O'Donell" <carlos@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>,
Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: Marcus Shawcroft <marcus.shawcroft@linaro.org>,
"libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: [PATCH] [AArch64] Define BE loader name.
Date: Wed, 08 Jan 2014 22:43:00 -0000 [thread overview]
Message-ID: <52CDD48A.80009@redhat.com> (raw)
In-Reply-To: <CA+=Sn1kwJCEV+u+6Z0WwOJLEnP=EjCpVp468e7ywSCJK=KxCwg@mail.gmail.com>
On 01/06/2014 12:16 PM, Andrew Pinski wrote:
>> Cavium / montavista do have the option of creating a symlink in order
>> to ease the transition.
>
> No this still broken.
We need technical arguments from both sides to reach consensus.
Marcus has to come up with real reasons for needing the new dynamic
linker name.
Andrew, you need to come up with concrete reasons for not wanting to use
a symlink or a copy.
This is *exactly* the same kind of change we made for the 32-bit ARM
hard-float dynamic linker name change.
The only wrinkle is that a symlink doesn't actually work:
https://sourceware.org/ml/libc-alpha/2012-10/msg00670.html
If Markus is suggesting using a symlink he'll have to look into the
problem I posted, because the last time I checked the symlink setup
didn't work and required a hack to be used until all binaries had
been migrated.
Thankfully in the case of the hard-float dynamic linker name change
we had consensus that the name change was needed to support a mixed
environment.
Cheers,
Carlos.
next prev parent reply other threads:[~2014-01-08 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 17:38 Marcus Shawcroft
2014-01-01 19:31 ` pinskia
2014-01-01 19:57 ` pinskia
2014-01-06 11:06 ` Marcus Shawcroft
2014-01-06 17:16 ` Andrew Pinski
2014-01-08 22:43 ` Carlos O'Donell [this message]
2014-01-13 18:17 ` Steve McIntyre
2014-01-17 23:04 ` Andrew Pinski
2014-01-20 15:53 ` Marcus Shawcroft
2014-01-20 16:13 ` Joseph S. Myers
2014-01-20 16:15 ` Policy: Require new dynamic loader names for entirely new ABIs? Carlos O'Donell
2014-01-20 17:10 ` Steve McIntyre
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=52CDD48A.80009@redhat.com \
--to=carlos@redhat.com \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@gmail.com \
--cc=marcus.shawcroft@linaro.org \
--cc=pinskia@gmail.com \
/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).