public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: Andrew Haley <aph@redhat.com>
Cc: Roland McGrath <roland@hack.frob.com>,
	libc-ports@sourceware.org, 	steve.mcintyre@linaro.org
Subject: Re: New path for ld.so on ARM hard fp
Date: Thu, 26 Apr 2012 03:41:00 -0000	[thread overview]
Message-ID: <CADZpyiyZgQGozxaBV7+q6JnNrJapuQnnZK4nr6tPMupHHZzF6Q@mail.gmail.com> (raw)
In-Reply-To: <4F9515D5.60804@redhat.com>

On Mon, Apr 23, 2012 at 4:41 AM, Andrew Haley <aph@redhat.com> wrote:
> On 04/14/2012 05:34 PM, Carlos O'Donell wrote:
>> On Fri, Apr 13, 2012 at 1:35 PM, Roland McGrath <roland@hack.frob.com> wrote:
>>>> Mmm, Joseph is away.  Would one of the regular ARM libc maintainers
>>>> like to pick this up?
>>>
>>> Only Joseph is authoritative.
>>
>> The distro community has reached consensus.
>>
>> IMO the glibc community should rely on the experience of the distro
>> community to guide us on such issues.
>>
>> I plan to create the change, test it, post the patch, ask for review
>> and commit as long as others don't see anything technically wrong with
>> this change.
>>
>> During that time I will attempt to get Joseph's feedback on the
>> change, but may fail to do so. I don't see that this blocks the patch
>> checkin to our development *trunk*.
>
> What's happening with this?

I just finished a set of WIP patches for this. I'll post them tomorrow morning.

Cheers,
Carlos.

  reply	other threads:[~2012-04-26  3:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 17:27 Andrew Haley
2012-04-13 17:29 ` Andrew Haley
2012-04-13 17:35   ` Roland McGrath
2012-04-14 16:35     ` Carlos O'Donell
2012-04-23  8:42       ` Andrew Haley
2012-04-26  3:41         ` Carlos O'Donell [this message]
2012-04-26 21:09         ` [WIP] glibc: Use /lib/ld-linux-armhf.so.3 for ARM's -mfloat-abi=hard ABI Carlos O'Donell
2012-04-26 21:43           ` Roland McGrath
2012-04-26 22:03           ` Joseph S. Myers
2012-04-26 22:07             ` Roland McGrath
2012-05-05 21:06               ` Carlos O'Donell
2012-05-05 21:48                 ` Joseph S. Myers
2012-05-05 21:52                 ` Carlos O'Donell
2012-05-05 23:17                   ` Joseph S. Myers
2012-05-06  2:18                     ` Carlos O'Donell
2012-05-06 12:13                       ` Joseph S. Myers
2012-05-06 21:36                         ` Carlos O'Donell
2012-05-06 22:41                           ` Joseph S. Myers
2012-05-07 18:47                   ` Roland McGrath
2012-05-07 18:57                     ` Carlos O'Donell
2012-05-07 19:55                       ` Roland McGrath
2012-05-07 20:00                         ` Carlos O'Donell
2012-05-07 20:00                           ` Carlos O'Donell
2012-05-07 19:11                     ` Joseph S. Myers
2012-05-07 19:41                       ` Roland McGrath
2012-05-07 20:52                         ` Joseph S. Myers
2012-05-07 21:31                           ` Roland McGrath
2012-05-01  4:48             ` Khem Raj
2012-05-01 10:09               ` Joseph S. Myers
2012-04-27  2:18           ` Mike Frysinger
2012-04-27 12:57             ` Carlos O'Donell
2012-04-19 19:49 ` New path for ld.so on ARM hard fp 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=CADZpyiyZgQGozxaBV7+q6JnNrJapuQnnZK4nr6tPMupHHZzF6Q@mail.gmail.com \
    --to=carlos@systemhalted.org \
    --cc=aph@redhat.com \
    --cc=libc-ports@sourceware.org \
    --cc=roland@hack.frob.com \
    --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).