From: Steve McIntyre <steve.mcintyre@linaro.org>
To: Marcus Shawcroft <marcus.shawcroft@linaro.org>
Cc: libc-ports@sourceware.org,
Carlos O'Donell <carlos@systemhalted.org>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH] AArch64: Tag ARM and AArch64 binaries in the ldconfig cache
Date: Tue, 04 Dec 2012 13:13:00 -0000 [thread overview]
Message-ID: <20121204131215.GA9979@linaro.org> (raw)
In-Reply-To: <CABXK9nepXY0qKfw7abrU_ffjEQgmnEiy_66B1GuBaeLf=ra6Ow@mail.gmail.com>
On Tue, Dec 04, 2012 at 01:02:38PM +0000, Marcus Shawcroft wrote:
>On 3 December 2012 15:25, Steve McIntyre <steve.mcintyre@linaro.org> wrote:
>> Hey guys,
>>
>> Splitting up code as requested. Here's patch #1 for AArch64.
>>
>> =======================================
>> Tag ARM and AArch64 binaries in the ldconfig cache
>>
>> * sysdeps/unix/sysv/linux/aarch64/readelflib.c: New file.
>>
>> Add the correct tags for ARM and AArch64 libraries in the ldconfig
>> cache for AArch64.
>
>
>Steve, Rather than replicate the code from arm/readelflib.c into
>aarch64/readelflib.c I'll apply the attached patch which uses the
>include mechanism you originally propsed here:
>
>http://sourceware.org/ml/libc-ports/2012-11/msg00111.html
Lovely, thanks. :-)
Cheers,
--
Steve McIntyre steve.mcintyre@linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
prev parent reply other threads:[~2012-12-04 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 15:26 Steve McIntyre
2012-12-03 15:28 ` [PATCH] AArch64: Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 cache Steve McIntyre
2012-12-04 12:52 ` Marcus Shawcroft
2012-12-04 13:02 ` [PATCH] AArch64: Tag ARM and AArch64 binaries in the ldconfig cache Marcus Shawcroft
2012-12-04 13:13 ` Steve McIntyre [this message]
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=20121204131215.GA9979@linaro.org \
--to=steve.mcintyre@linaro.org \
--cc=carlos@systemhalted.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@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).