This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
test-in-container: Moving a test to a particular location *before* execution?
- From: Carlos O'Donell <carlos at redhat dot com>
- To: DJ Delorie <dj at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Tue, 10 Dec 2019 14:37:15 -0500
- Subject: test-in-container: Moving a test to a particular location *before* execution?
DJ,
In developing tests for dynamic string token substitution
in DT_RUNPATH, DT_PRATH and LD_PRELOAD etc, I found that
$ORIGIN is hard to test because I want this kind of behaviour:
(a) Create the chroot.
(b) Move the test into the chroot into the $ORIGIN expected location.
(c) Run the test in the container.
The (c) part doesn't work like I expect because test-container
is running the binary relative to the build path.
I think I might need some kind of env var like TEST_RUN_FROM=/path/
where the binary is copied into the path and then the $filename is
executed from that path.
Does that make sense?
For DSOs and other files I can move them all into the chroot by
using the setup script, but the executable can't be moved like
that because the target of execution is given to test-container by
the makefile target.
--
Cheers,
Carlos.