This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] test-in-container: Do not set GCONV_PATH, LOCPATH
- From: DJ Delorie <dj at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 20 May 2019 14:19:06 -0400
- Subject: Re: [PATCH] test-in-container: Do not set GCONV_PATH, LOCPATH
There's code in test-container.c to not propogate environment variables
to the in-container test:
while (is_env_setting (argv[1]))
{
/* If there are variables we do NOT want to propogate, this
is where the test for them goes. */
{
That way we can treate test-container itself like any other testcase,
and have it worry about "cleaning" the environment for the contained
tests.
The source/build directories are loop-mounted inside the container, so
such environment variables *should* work if set, and there were some
test when I was testing everything in containers that still needed those
vars set. I didn't investigate why.