Pádraig Brady wrote: > > FAIL: tests/misc/env > > These are due to `env .` being treated as command not found, > rather than cannot invoke. I saw reference that windows > createprocess may strip trailing '.', so I'm guessing './' may be ok here. > Attached uses ./ in this context in these tests.
This change doesn't help, for me. Both /usr/bin/env and src/env fail with "No such file or directory" when the argument is . or ./ — no difference. The only way I can make 'env' return with exit code 126 is src/env sh -c 'exit 126' Bruno
