public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Steve McIntyre <steve.mcintyre@linaro.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH 2/4] Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache
Date: Mon, 03 Dec 2012 15:19:00 -0000	[thread overview]
Message-ID: <20121203151810.GA22509@einval.com> (raw)
In-Reply-To: <CAE2sS1jz3ZUh7fHq2hWQU2odbfLCwn4wm_44hTLg_rW2RP3jiw@mail.gmail.com>

On Fri, Nov 30, 2012 at 11:37:48AM -0500, Carlos O'Donell wrote:
>On Fri, Nov 30, 2012 at 10:01 AM, Steve McIntyre
><steve.mcintyre@linaro.org> wrote:
>> On 28 November 2012 20:58, Carlos O'Donell <carlos@systemhalted.org> wrote:
>>>On Mon, Nov 26, 2012 at 03:04:34PM +0000, Steve McIntyre wrote:
>>>>Use the new FLAG_AARCH64_LIB64 ldconfig cache tag for AArch64,
>>>>similarly to the way tags are handled for other architectures.
>>>>
>>>>========================================================
>>>>
>>>>Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache
>>>>
>>>>      * sysdeps/unix/sysv/linux/aarch64/dl-cache.h: New file.
>>>>
>>>>Signed-off-by: Steve McIntyre <steve.mcintyre@linaro.org>
>>>
>>> Reviewed-by: Carlos O'Donell  <carlos@systemhalted.org>
>>>
>>> This looks good to me.
>>>
>>> Markus, as the AArch64 maintainer, should have the final word and
>>> check it in.
>>>
>>> Feel free to include my Reviewed-by: in the git commit logs to track
>>> reviews.
>>
>> Hmmm, problem: this adds checking for the new FLAG_AARCH64_LIB64 at
>> runtime in ld.so, but nobody has (yet!) committed the code that will
>> add that flag from ldconfig (in patch #3 in my set). That's partly my
>> fault for not stating a direct dependency, I guess, but we'll need to
>> fix that ASAP. Would you prefer to revert *this* patch or take that
>> one too?
>
>Thanks, I hadn't noticed the dependency.
>
>Please work on getting this fixed ASAP.
>
>We want AArch64 into 2.17.
>
>> Related to Joseph's comment about #1 in the set (tagging binaries
>> based on interpreter names): splitting up ARM and AArch64 patches. I
>> can easily split #1 that way if preferred, but to my mind it makes no
>> sense to split #3 as it's a lump of common code that will run on both
>> ARM and AArch64. What do people think about that, please?
>
>Split them up please.
>
>Push them out again for review, and CC me and Joseph.

OK. Coming in a mo, in two separate threads. I'll CC you both on both
threads too.

Cheers,
-- 
Steve McIntyre                                steve.mcintyre@linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

  reply	other threads:[~2012-12-03 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 15:02 [PATCH 1/4] Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 Steve McIntyre
2012-11-26 15:05 ` [PATCH 2/4] Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache Steve McIntyre
2012-11-28 20:58   ` Carlos O'Donell
2012-11-29 10:40     ` Marcus Shawcroft
2012-11-30 15:01     ` Steve McIntyre
2012-11-30 16:38       ` Carlos O'Donell
2012-12-03 15:19         ` Steve McIntyre [this message]
2013-02-08 20:29   ` Andreas Schwab
2012-11-26 15:10 ` [PATCH 3/4] Tag ARM and AArch64 binaries " Steve McIntyre
2012-11-26 16:32 ` [PATCH 1/4] Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 Joseph S. Myers

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=20121203151810.GA22509@einval.com \
    --to=steve.mcintyre@linaro.org \
    --cc=carlos@systemhalted.org \
    --cc=libc-ports@sourceware.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).