public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Sunil Pandey <skpgkp2@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>,
	 Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Force DT_RPATH for --enable-hardcoded-path-in-tests
Date: Thu, 9 May 2024 20:55:51 -0700	[thread overview]
Message-ID: <CAMAf5_co4qcpbT_tPBe-zt77s6-ucq3oq3T_nC2uaP8Wh=B6sg@mail.gmail.com> (raw)
In-Reply-To: <20240510030701.834418-1-hjl.tools@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]

On Thu, May 9, 2024 at 8:07 PM H.J. Lu <hjl.tools@gmail.com> wrote:

> On Fedora 40/x86-64, linker enables --enable-new-dtags by default which
> generates DT_RUNPATH instead of DT_RPATH.  Unlike DT_RPATH, DT_RUNPATH
> only applies to DT_NEEDED entries in the executable and doesn't applies
> to DT_NEEDED entries in shared libraries which are loaded via DT_NEEDED
> entries in the executable.  Some glibc tests have libstdc++.so.6 in
> DT_NEEDED, which has libm.so.6 in DT_NEEDED.  When DT_RUNPATH is generated,
> /lib64/libm.so.6 is loaded for such tests.  If the newly built glibc is
> older than glibc 2.36, these tests fail with
>
> assert/tst-assert-c++:
> /export/build/gnu/tools-build/glibc-gitlab-release/build-x86_64-linux/libc.so.6:
> version `GLIBC_2.36' not found (required by /lib64/libm.so.6)
> assert/tst-assert-c++:
> /export/build/gnu/tools-build/glibc-gitlab-release/build-x86_64-linux/libc.so.6:
> version `GLIBC_ABI_DT_RELR' not found (required by /lib64/libm.so.6)
>
> Pass -Wl,--disable-new-dtags to linker when building glibc tests with
> --enable-hardcoded-path-in-tests.  This fixes BZ #31719.
>
> Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
> ---
>  Makeconfig | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/Makeconfig b/Makeconfig
> index 61ff1d0d9b..59e21d4c82 100644
> --- a/Makeconfig
> +++ b/Makeconfig
> @@ -607,10 +607,13 @@ link-libc-rpath-link = -Wl,-rpath-link=$(rpath-link)
>  # before the expansion of LDLIBS-* variables).
>
>  # Tests use -Wl,-rpath instead of -Wl,-rpath-link for
> -# build-hardcoded-path-in-tests.
> +# build-hardcoded-path-in-tests.  Add -Wl,--disable-new-dtags to force
> +# DT_RPATH instead of DT_RUNPATH which only applies to DT_NEEDED entries
> +# in the executable and doesn't applies to DT_NEEDED entries in shared
> +# libraries which are loaded via DT_NEEDED entries in the executable.
>  ifeq (yes,$(build-hardcoded-path-in-tests))
> -link-libc-tests-rpath-link = $(link-libc-rpath)
> -link-test-modules-rpath-link = $(link-libc-rpath)
> +link-libc-tests-rpath-link = $(link-libc-rpath) -Wl,--disable-new-dtags
> +link-test-modules-rpath-link = $(link-libc-rpath) -Wl,--disable-new-dtags
>  else
>  link-libc-tests-rpath-link = $(link-libc-rpath-link)
>  link-test-modules-rpath-link =
> --
> 2.45.0
>
>
I would like to backport this patch to release branches up to 2.28.
Any comments or objections?

--Sunil

       reply	other threads:[~2024-05-10  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240510030701.834418-1-hjl.tools@gmail.com>
2024-05-10  3:55 ` Sunil Pandey [this message]
2024-05-10  3:58   ` H.J. Lu

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='CAMAf5_co4qcpbT_tPBe-zt77s6-ucq3oq3T_nC2uaP8Wh=B6sg@mail.gmail.com' \
    --to=skpgkp2@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@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).