From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>, <libc-ports@sourceware.org>
Subject: Re: [PATCH] aarch64: use lib64 as default lib and slib directory
Date: Fri, 15 Mar 2013 16:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1303151613210.7765@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFqB+PzMwhAQSc=nnA4cA6DQpnJsTv0=_s0e5w70pN9s6b8w0w@mail.gmail.com>
On Fri, 15 Mar 2013, Marcus Shawcroft wrote:
> Hi,
>
> This patch seems to have the effect of moving the dynamic linker to
> /lib64, do we need some ldd-rewrite.sed foo hooked into
> ports/sysdeps/unix/sysv/linux/aarch64/configure.in ?
How does s390 glibc handle dynamic linker and libraries in different
directories? If it doesn't, maybe that illustrates that keeping the
dynamic linker in /lib with other libraries in /lib64 really isn't such a
good idea after all and /lib64 should be used consistently or not at
all....
(ldd-rewrite.sed may be needed anyway, I just don't think it will help
with the issue to which you refer.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-03-15 16:16 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
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 [this message]
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.1303151613210.7765@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@gmail.com \
--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).