public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at deneb dot enyo.de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/25846] Provide method to show loader search directories Date: Mon, 04 May 2020 04:14:20 +0000 [thread overview] Message-ID: <bug-25846-131-SwA7zQ3Du4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25846-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25846 Florian Weimer <fw at deneb dot enyo.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fw at deneb dot enyo.de --- Comment #4 from Florian Weimer <fw at deneb dot enyo.de> --- (In reply to Dan Nicholson from comment #3) > OK, I'll bring the patch over to the mailing list and see about the > copyright assignment. Thanks. > I see what you're saying about having it in ld.so instead of ldconfig. I think we eventually need both, so starting with ldconfig is fine. > Unfortunately, knowing the path to ld.so can be difficult. What do you think > about calling ld.so in the appropriate mode from a well known tool like ldd > does as a convenience? We could install ld.so as a program in /usr/bin, as a separate change. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-04 4:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-17 22:38 [Bug dynamic-link/25846] New: " nicholson at endlessm dot com 2020-04-17 22:38 ` [Bug dynamic-link/25846] " nicholson at endlessm dot com 2020-04-17 22:47 ` ijaffery7 at gmail dot com 2020-04-20 9:13 ` fweimer at redhat dot com 2020-05-03 20:49 ` nicholson at endlessm dot com 2020-05-04 4:14 ` fw at deneb dot enyo.de [this message] 2022-01-27 15:45 ` fweimer at redhat dot com
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=bug-25846-131-SwA7zQ3Du4@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).