From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>, Fangrui Song <i@maskray.me>
Subject: Re: Failing DT_RELR tests and --enable-hardcoded-path-in-tests?
Date: Fri, 28 Oct 2022 15:17:48 -0700 [thread overview]
Message-ID: <CAMe9rOp4O=QJzH=0A=w9yCOrHLMyi7R27g3pCcm8txdHUHTphg@mail.gmail.com> (raw)
In-Reply-To: <fcee9fef-447a-2461-61bf-9ca4b446cb47@redhat.com>
On Fri, Oct 28, 2022 at 2:37 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> HJ,
>
> In my testing on the recently about to be released Fedora 37 I noted the
> following two failures:
>
> tests.sum:FAIL: elf/tst-relr3
> tests.sum:FAIL: elf/tst-relr4
>
> cat elf/tst-relr3.test-result
> FAIL: elf/tst-relr3
> original exit status 127
>
> env GCONV_PATH=/home/carlos/build/glibc-review/iconvdata LOCPATH=/home/carlos/build/glibc-review/localedata LC_ALL=C /home/carlos/build/glibc-review/elf/tst-relr3 > /home/carlos/build/glibc-review/elf/tst-relr3.out; \
> ../scripts/evaluate-test.sh elf/tst-relr3 $? false false > /home/carlos/build/glibc-review/elf/tst-relr3.test-result
> ...
> /home/carlos/build/glibc-review/elf/tst-relr3: error while loading shared libraries: tst-relr-mod3b.so: cannot open shared object file: No such file or directory
>
> In the hardcoded path mode we do not add any additional paths to search
> for tst-relr-mod3b.so that is depended upon by tst-relr-mod3a.so.
>
> Under Fedora we have DT_RUNPATH only:
> 0x000000000000001d (RUNPATH) Library runpath: [/home/carlos/build/glibc-review:/home/carlos/build/glibc-review/math:/home/carlos/build/glibc-review/elf:/home/carlos/build/glibc-review/dlfcn:/home/carlos/build/glibc-review/nss:/home/carlos/build/glibc-review/nis:/home/carlos/build/glibc-review/rt:/home/carlos/build/glibc-review/resolv:/home/carlos/build/glibc-review/mathvec:/home/carlos/build/glibc-review/support:/home/carlos/build/glibc-review/crypt:/home/carlos/build/glibc-review/nptl]
>
> Do we need to add some rpath usage here when building the module?
Yes.
> Suggestions?
Here is a patch:
https://patchwork.sourceware.org/project/glibc/list/?series=13666
--
H.J.
prev parent reply other threads:[~2022-10-28 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 21:37 Carlos O'Donell
2022-10-28 22:17 ` H.J. Lu [this message]
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='CAMe9rOp4O=QJzH=0A=w9yCOrHLMyi7R27g3pCcm8txdHUHTphg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=carlos@redhat.com \
--cc=i@maskray.me \
--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).