public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28455] -Wl,--enable-new-dtags doesn't work
Date: Mon, 24 Jan 2022 13:54:39 +0000 [thread overview]
Message-ID: <bug-28455-131-zX0OkYNbWa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28455-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28455
--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=114d07fd9a54684cb67b02174f2c48d19f3e2502
commit 114d07fd9a54684cb67b02174f2c48d19f3e2502
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Fri Oct 15 06:33:05 2021 -0700
Add and use link-test-modules-rpath-link [BZ #28455]
DT_RUNPATH is only used to find the immediate dependencies of the
executable or shared object containing the DT_RUNPATH entry:
1. Define link-test-modules-rpath-link if $(build-hardcoded-path-in-tests)
is yes.
2. Use $(link-test-modules-rpath-link) in build-module-helper so that
test modules can dlopen modules with DT_RUNPATH.
3. Add a test to show why link-test-modules-rpath-link is needed.
This partially fixes BZ #28455.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-24 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 12:11 [Bug dynamic-link/28455] New: " hjl.tools at gmail dot com
2021-10-15 12:16 ` [Bug dynamic-link/28455] " hjl.tools at gmail dot com
2021-10-15 12:48 ` hjl.tools at gmail dot com
2021-10-15 13:32 ` hjl.tools at gmail dot com
2021-10-22 14:53 ` hjl.tools at gmail dot com
2021-10-22 23:27 ` hjl.tools at gmail dot com
2021-10-29 13:30 ` sam at gentoo dot org
2021-12-13 15:32 ` cvs-commit at gcc dot gnu.org
2022-01-03 12:42 ` hjl.tools at gmail dot com
2022-01-04 13:54 ` cvs-commit at gcc dot gnu.org
2022-01-24 13:54 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-24 13:55 ` hjl.tools at gmail 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-28455-131-zX0OkYNbWa@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: 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).