public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
	Andreas Schwab <schwab@suse.de>,
	Marcus Shawcroft <marcus.shawcroft@linaro.org>,
	<libc-ports@sourceware.org>
Subject: Re: [PATCH] aarch64: use lib64 as default lib and slib directory
Date: Wed, 13 Mar 2013 16:29:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1303131628000.19781@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20130313134646.GU12913@tucnak.redhat.com>

On Wed, 13 Mar 2013, Jakub Jelinek wrote:

> > However, there was some recent discussion about this in gcc.
> > 
> > Jakub, What's the status?
> 
> No progress there, see the
> http://gcc.gnu.org/ml/gcc-patches/2013-03/msg00288.html
> thread.  I'd really like to get it resolved before we cut
> GCC 4.8.0-rc1 this week.

If it does change to /lib64, it would seem odd for the dynamic linker path 
(GLIBC_DYNAMIC_LINKER in aarch64-linux.) to stay as 
/lib/ld-linux-aarch64.so.1 rather than also being in /lib64 (although s390 
also puts the 64-bit dynamic link in /lib).

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2013-03-13 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 11:33 Andreas Schwab
2013-03-13 13:42 ` Carlos O'Donell
2013-03-13 13:47   ` Jakub Jelinek
2013-03-13 14:57     ` Carlos O'Donell
2013-03-14  8:40       ` Marcus Shawcroft
2013-03-13 16:29     ` Joseph S. Myers [this message]
2013-03-14  7:58       ` Jakub Jelinek
2013-03-14  8:46       ` Marcus Shawcroft
2013-03-14 15:12         ` Carlos O'Donell
2013-03-18 11:25           ` Marcus Shawcroft
2013-03-18 11:41             ` Jakub Jelinek
2013-03-15 14:53 ` Marcus Shawcroft
2013-03-15 16:16   ` Joseph S. Myers
2013-03-15 18:11     ` Mike Frysinger
2013-03-18 11:53   ` [PATCH] Add support for rtld directory different from " Andreas Schwab

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=Pine.LNX.4.64.1303131628000.19781@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=jakub@redhat.com \
    --cc=libc-ports@sourceware.org \
    --cc=marcus.shawcroft@linaro.org \
    --cc=schwab@suse.de \
    /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).