From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
Libc-alpha <libc-alpha@sourceware.org>,
Mark Hatle <mark.hatle@kernel.crashing.org>
Subject: Re: Yocto prelink status
Date: Wed, 19 Jan 2022 20:28:12 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2201192022150.24573@digraph.polyomino.org.uk> (raw)
In-Reply-To: <fc0acdcb-67ee-23ae-cc23-b460410f010e@linaro.org>
On Wed, 19 Jan 2022, Adhemerval Zanella via Libc-alpha wrote:
> Recent discussions on glibc maillist about prelink supported is leading
> us to deprecate and remove its support on glibc. Last year it was hinted
> that Yocto seems to be maintained the project, although without much
> development [1].
Also it's not clear there are any active patch reviewers any more, at
least based on my experience with AArch64 support fixes (sent to Mark in
May 2020; the yocto@yoctoproject.org mailing list rejects email from
non-subscribers, or did at that time; see https://github.com/jsm28/prelink
branch cross_prelink_aarch64_fixes for a git tree with those fixes based
on a merge of the cross_prelink branch into cross_prelink_aarch64).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-01-19 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 19:52 Adhemerval Zanella
2022-01-19 20:28 ` Joseph Myers [this message]
2022-01-20 22:51 Richard Purdie
2022-01-21 10:58 ` Phil Blundell
2022-01-21 16:23 ` Szabolcs Nagy
2022-01-21 17:09 ` Phil Blundell
2022-02-03 15:26 ` Richard Purdie
2022-02-03 15:43 ` Mark Hatle
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=alpine.DEB.2.22.394.2201192022150.24573@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=mark.hatle@kernel.crashing.org \
--cc=nicolas.dechesne@linaro.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).