From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Carlos O'Donell <carlos@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH 0/3] Remove prelink support
Date: Thu, 03 Feb 2022 15:29:28 +0000 [thread overview]
Message-ID: <ca8ab8d225cda0956a6e0a886b32c894fe3c02e4.camel@linuxfoundation.org> (raw)
In-Reply-To: <6756d321-a537-48f1-931c-c68a12dd2309@redhat.com>
On Wed, 2022-01-26 at 23:59 -0500, Carlos O'Donell wrote:
> On 1/21/22 12:29, Adhemerval Zanella via Libc-alpha wrote:
> > As discussed recently on maillist [1], prelink is deprecated in
> > practice:
>
> This goes in the right direction.
>
> I think we should review this for glibc 2.36.
>
> Leaving glibc 2.35 as the last release with prelink support.
Can I confirm that by the above, you mean that prelink is almost certain to be
removed after 2.35 is released?
Yocto Project has an LTS due soon and this does influence what we do there a
little which is why I'm asking specifically.
I'm saddened but resigned to it, the sad reality is there aren't enough people
to maintain everything and the utility of prelink is now questionable.
Cheers,
Richard
next prev parent reply other threads:[~2022-02-03 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 17:29 Adhemerval Zanella
2022-01-21 17:29 ` [PATCH 1/3] elf: " Adhemerval Zanella
2022-01-21 17:29 ` [PATCH 2/3] malloc: Remove LD_TRACE_PRELINKING usage from mtrace Adhemerval Zanella
2022-01-21 18:05 ` Siddhesh Poyarekar
2022-01-21 17:29 ` [PATCH 3/3] elf: Remove LD_USE_LOAD_BIAS Adhemerval Zanella
2022-01-24 18:55 ` [PATCH 0/3] Remove prelink support Adhemerval Zanella
2022-01-27 4:59 ` Carlos O'Donell
2022-02-03 15:29 ` Richard Purdie [this message]
2022-02-03 16:30 ` Adhemerval Zanella
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=ca8ab8d225cda0956a6e0a886b32c894fe3c02e4.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@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).