From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Always set l in _dl_init_paths (Bug 23462).
Date: Wed, 16 Oct 2019 13:31:00 -0000 [thread overview]
Message-ID: <79397430-ce3f-446e-eadb-18531ad5ae79@redhat.com> (raw)
In-Reply-To: <87bluh53z3.fsf@oldenburg2.str.redhat.com>
On 10/16/19 7:23 AM, Florian Weimer wrote:
> * Carlos O'Donell:
>
>>> Does this change enable DT_RUNPATH/DT_RPATH for statically linked
>>> binaries? Should that receive a NEWS entry and a test?
>>
>> It does enable DT_RUNPATH/DT_RPATH for statically linked binaries,
>> and we should probably add a test for that?
>
> Right.
Perfect, let me do that. I'll add another test.
>> If you think the semantic change here is wrong, please call that out.
>
> No, I think it would be a useful feature. I sort-of ran into this here:
>
> resolv/tst-idna_name_classify: Isolate from system libraries
> <https://sourceware.org/ml/libc-alpha/2019-10/msg00338.html>
>
> And I briefly wondered if we should do this automatically for
> --enable-hardcoded-path-in-tests.
>
> Thanks,
> Florian
>
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-10-16 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 0:01 Carlos O'Donell
2019-10-15 16:24 ` Carlos O'Donell
2019-10-16 9:54 ` Florian Weimer
2019-10-16 11:15 ` Carlos O'Donell
2019-10-16 11:23 ` Florian Weimer
2019-10-16 13:31 ` Carlos O'Donell [this message]
2019-10-25 1:16 ` Carlos O'Donell
2019-10-25 8:37 ` Florian Weimer
2019-10-25 12:55 ` Carlos O'Donell
2021-03-05 18:25 [PATCH] elf: Always set l in _dl_init_paths (bug 23462) Florian Weimer
2021-03-08 22:26 ` Carlos O'Donell
2021-03-09 5:39 ` Navin P
2021-03-09 6:05 ` Florian Weimer
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=79397430-ce3f-446e-eadb-18531ad5ae79@redhat.com \
--to=carlos@redhat.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).