diff options
| author | H.J. Lu <hjl.tools@gmail.com> | 2024-05-09 20:07:01 -0700 |
|---|---|---|
| committer | H.J. Lu <hjl.tools@gmail.com> | 2024-05-10 05:47:09 -0700 |
| commit | 8e30f03744837a85e33d84ccd34ed3abe30d37c3 (patch) | |
| tree | b216f3f34576bac88cf9a34431a66f6f0a3a7b12 /manual | |
| parent | 2d0e16a01b73bf64f2ced02074cc3879893ffdab (diff) | |
| download | glibc-8e30f03744837a85e33d84ccd34ed3abe30d37c3.tar.gz glibc-8e30f03744837a85e33d84ccd34ed3abe30d37c3.tar.xz glibc-8e30f03744837a85e33d84ccd34ed3abe30d37c3.zip | |
Force DT_RPATH for --enable-hardcoded-path-in-tests
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> (cherry picked from commit 2dcaf70643710e22f92a351e36e3cff8b48c60dc)
Diffstat (limited to 'manual')
0 files changed, 0 insertions, 0 deletions