From: Thomas Schwinge <thomas@codesourcery.com>
To: Roland McGrath <roland@hack.frob.com>, <bug-hurd@gnu.org>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Carlos O'Donell <carlos@redhat.com>, <gcc@gcc.gnu.org>
Subject: Hurd: /lib/ld.so vs. /lib/ld.so.1 (was: Policy: Require new dynamic loader names for entirely new ABIs?)
Date: Wed, 22 Jan 2014 15:52:00 -0000 [thread overview]
Message-ID: <87vbxc81c6.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1401220347300.3624@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hi!
On Wed, 22 Jan 2014 03:54:31 +0000, "Joseph S. Myers" <joseph@codesourcery.com> wrote:
> On Tue, 21 Jan 2014, Carlos O'Donell wrote:
> > > x86 Hurd (32-bit, hard-float): /lib/ld.so (that is, GCC uses that name
> > > with -dynamic-linker so in PT_INTERP; my understanding of
> > > shlib-versions is that it gets the SONAME ld.so.1 by default).
> >
> > Is that a bug?
>
> I don't know. Thomas?
For x86 Hurd, GCC has been specifying »-dynamic-linker /lib/ld.so« in
LINK_SPEC since forever (1995, or earlier), and Debian glibc has had the
following since forever (2002, or earlier):
ifeq ($(DEB_HOST_GNU_SYSTEM),gnu)
# Why doesn't the glibc makefile install this?
ln -sf ld.so.1 $(tmpdir)/$@/lib/ld.so
endif
Roland, do you have any recollection of this? Assuming that /lib/ld.so.1
is the "official" name, I suppose GCC should be changed, and then Debian
could drop the symbolic link after a transition period (full archive
rebuilt, etc.).
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next parent reply other threads:[~2014-01-22 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52DD4BB8.1090901@redhat.com>
[not found] ` <52DD56C8.109@redhat.com>
[not found] ` <Pine.LNX.4.64.1401212208100.25161@digraph.polyomino.org.uk>
[not found] ` <52DF3E13.6050408@redhat.com>
[not found] ` <Pine.LNX.4.64.1401220347300.3624@digraph.polyomino.org.uk>
2014-01-22 15:52 ` Thomas Schwinge [this message]
2014-01-29 6:26 ` Roland McGrath
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=87vbxc81c6.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=bug-hurd@gnu.org \
--cc=carlos@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.frob.com \
/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).