public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Michael Hope <michael.hope@linaro.org>
To: Steve McIntyre <steve.mcintyre@linaro.org>
Cc: cross-distro@lists.linaro.org, gcc-patches@gcc.gnu.org,
		Adam Conrad <adconrad@debian.org>,
	libc-ports@sourceware.org, 	linaro-toolchain@lists.linaro.org,
	Jeff Law <law@redhat.com>
Subject: Re: Phone call (was Re: Armhf dynamic linker path)
Date: Wed, 11 Apr 2012 23:22:00 -0000	[thread overview]
Message-ID: <CANLjY-k73dZJmE9YOvy-fG3rH_L-Ycz6tt4tsV7CKo3t5phSoA@mail.gmail.com> (raw)
In-Reply-To: <20120411223755.GD25263@einval.com>

On 12 April 2012 10:38, Steve McIntyre <steve.mcintyre@linaro.org> wrote:
> On Wed, Apr 11, 2012 at 02:06:09AM +0100, Steve McIntyre wrote:
>>
>>And here's the details as promised.
>>
>>I've started a wiki page at
>>
>>https://wiki.linaro.org/OfficeofCTO/HardFloat/LinkerPathCallApr2012
>>
>>with a strawman agenda for now, and a Doodle poll at
>>
>>http://www.doodle.com/93bitkqeb7auyxn7
>>
>>to see when the best time is for the call on Thursday/Friday. Please
>>fill in the times that work for you ASAP and I'll announce the result
>>during Wednesday. Ideally we'd like stakeholders from all the relevant
>>distros and the upstream toolchain developers to be there, able to
>>represent their groups and (importantly) able to make a decision here
>>on what we should do.
>>
>>Apologies for the short notice, but we need a decision quickly.
>
> And the best time turns out to be Friday at 15:00 UTC (16:00 BST,
> 11:00 EDT etc.). Of the 10 people who responded in the poll, the only
> person who can't make that time is Michael in .nz. Sorry, Michael.

All good.  My vote is for /lib/ld-arm-linux-gnueabihf.so.3 as it:
 * is similar to /lib/ld-x86-64.so.2
 * keeps the libraries and loader in the same directory
 * doesn't invent a new /libhf directory
 * is easier to implement in GLIBC
 * is architecture and ABI unique
 * requires less change for distros where the hard float libraries are
already in /lib

I'm happy to do the GLIBC and GCC implementation.

-- Michael

       reply	other threads:[~2012-04-11 23:22 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 [this message]
     [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
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=CANLjY-k73dZJmE9YOvy-fG3rH_L-Ycz6tt4tsV7CKo3t5phSoA@mail.gmail.com \
    --to=michael.hope@linaro.org \
    --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=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).