From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH v2 1/3] elf: Remove prelink support
Date: Thu, 3 Feb 2022 16:57:47 -0300 [thread overview]
Message-ID: <f6171e09-22cd-ab0e-64e1-e23abbe54089@linaro.org> (raw)
In-Reply-To: <87r18jrcm9.fsf@oldenburg.str.redhat.com>
On 03/02/2022 16:09, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
>
>> diff --git a/NEWS b/NEWS
>> index 7b8febcb72..b9a3c90ac0 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -13,7 +13,9 @@ Major new features:
>>
>> Deprecated and removed features, and other changes affecting compatibility:
>>
>> - [Add deprecations, removals and changes affecting compatibility here]
>> +* Support for prelink will be removed in the next release; this includes
>> + removal of the LD_TRACE_PRELINKING, and LD_USE_LOAD_BIAS, environment
>> + variables and their functionality in the dynamic loader.
>>
>> Changes to build and runtime requirements:
>>
>> @@ -187,9 +189,8 @@ Deprecated and removed features, and other changes affecting compatibility:
>> been removed. There are widely-deployed out-of-process alternatives for
>> catching coredumps and backtraces.
>>
>> -* Support for prelink will be removed in the next release; this includes
>> - removal of the LD_TRACE_PRELINKING, and LD_USE_LOAD_BIAS, environment
>> - variables and their functionality in the dynamic loader.
>> +* The prelink support has been removed. Prelinked binaries and libraries
>> + work as if prelinked is disabled.
>>
>> Changes to build and runtime requirements:
>
> Something went wrong with the rebase there, I think. The old entry
> should not be changed.
Yeah, I will remove this change.
next prev parent reply other threads:[~2022-02-03 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 18:57 [PATCH v2 0/3] " Adhemerval Zanella
2022-02-03 18:57 ` [PATCH v2 1/3] elf: " Adhemerval Zanella
2022-02-03 19:09 ` Florian Weimer
2022-02-03 19:57 ` Adhemerval Zanella [this message]
2022-02-10 6:10 ` Siddhesh Poyarekar
2022-02-03 18:57 ` [PATCH v2 2/3] malloc: Remove LD_TRACE_PRELINKING usage from mtrace Adhemerval Zanella
2022-02-03 18:57 ` [PATCH v2 3/3] elf: Remove LD_USE_LOAD_BIAS Adhemerval Zanella
2022-02-10 6:12 ` Siddhesh Poyarekar
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=f6171e09-22cd-ab0e-64e1-e23abbe54089@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=richard.purdie@linuxfoundation.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).