This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/24506] FAIL: elf/tst-pldd


https://sourceware.org/bugzilla/show_bug.cgi?id=24506

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to H.J. Lu from comment #2)
> (In reply to Florian Weimer from comment #1)
> > I believe this is because the test runs against the installed (system) pldd.
> > You can run the test directly this way, even though it does not fail.
> 
> Isn't it wrong to test the installed pldd?

Yes, like with any other test (which in a default build would attempt to run
against the installed glibc, if not statically linked).  The makefiles run the
test in such a way that the correct (in-tree) binary is tested.

Do you configure with --enable-hardcoded-path-in-tests?  It's not effective
here.  But that's also true for tests that require certain environment
variables.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]