public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] elf: Install a symbolic link to ld.so as /usr/bin/ld.so
Date: Mon, 6 Dec 2021 10:36:28 +1300	[thread overview]
Message-ID: <CAJ8wqtfMARnaQhKRN+B27FjQpuxUzEdUic3bQAvp0+4cFwokcA@mail.gmail.com> (raw)
In-Reply-To: <87lf10tc9l.fsf@oldenburg.str.redhat.com>

On Sun, 5 Dec 2021 at 08:13, Florian Weimer via Libc-alpha <
libc-alpha@sourceware.org> wrote:

>
> Some distribution discussions on this patch:
>
>   /usr/bin/ld.so as a symbolic link for the dynamic loader
>
>   <
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SA244MNX5CC5OED65SX3QNCLKDUKW7D3/
> >
>
>   <https://lists.debian.org/debian-glibc/2021/12/msg00001.html>
>   <https://lists.debian.org/debian-devel/2021/12/msg00032.html>
>   (thread wasn't Cc:ed to both lists throughout)


I think this is a good idea although I haven't thought incredibly hard
about it. I agree with Lennart that being able to readlink /usr/bin/ld.so
to get the default native dynamic linker path would be useful (although
there are probably other ways to meet that need).

Cheers,
mwh

      reply	other threads:[~2021-12-05 21:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 19:07 Florian Weimer
2021-11-23 15:56 ` Florian Weimer
2021-11-23 16:19 ` Andreas Schwab
2021-11-23 16:38   ` Florian Weimer
2021-11-24 17:00     ` Andreas Schwab
2021-12-03 14:05       ` Florian Weimer
2021-12-06 17:19         ` Andreas Schwab
2021-12-04 19:12 ` Florian Weimer
2021-12-05 21:36   ` Michael Hudson-Doyle [this message]

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=CAJ8wqtfMARnaQhKRN+B27FjQpuxUzEdUic3bQAvp0+4cFwokcA@mail.gmail.com \
    --to=michael.hudson@canonical.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).