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

["carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Florian Weimer from comment #3)
> (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.

Right, --enable-hardcoded-path-in-tests is not enough to make all tests work,
some tests require more setup e.g. env vars, containers (chroot), special
arguments.

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