On 04/03/2020 13:44, Marius Bakke wrote:
Pádraig Brady <address@hidden> writes: >>
I don't see /bin/env being used here.
Really? Can you send a trace of 'make check TESTS=tests/misc/env-S.pl'?
Curious how it is supposed to work...
Oops I typod my grep. I do see the /usr/bin/env now.
The reason is, where we run env with -i the PATH is cleared,
and the system then falls back to default paths:
$ strace -e execve src/env -i A=B env
execve("src/env", ["src/env", "-i", "A=B", "env"], 0x7ffcfede1638 /* 65 vars
*/) = 0
execve("/usr/bin/env", ["env"], 0x1cfa380 /* 1 var */) = 0
A=B
We could avoid that by specifying the path to our built env(1) instead.
I'll look at doing something with $abs_top_builddir/src/env