Follow-up Comment #1, bug #56831 (project findutils): As you're pointing out there are two issues here.
(1) Is the test suite overriding the user's choice of PATH? ... If yes, that would be a bug. (2) Should the behaviour of -printf %i follow GNU ls or the system ls? For (2), since POSIX doesn't specify -printf, the decision to follow GNU ls specifically is certainly acceptable. The option of emulating the system's ls seems like it would require a lot of code. This code would be hard to test since the maintainers would need to perform regression tests on every supported system (and, right now, there is no real notion of "supported system"; we attempt to support all systems that Autoconf can grok which have a standard-conforming hosted C implementation and on which the build tool dependencies can be built). I tried to reproduce this problem, and didn't discover a location in which $PATH was changed in this way. The test environment setup does prepend some directories, but these should only be source directories within the source tree and the build tree (if different). Do you have, perhaps, $ENV set to a file which unconditionally sets $PATH to eliminate the PATH setting you are selecting with /usr/bin/env? If you are, I'd suggest undetting $ENV. Otherwise, I think I need more data about what is happening for you. Try modifying init.cfg to print $PATH at the end of init.cfg. The output should turn up in tests/find/printf_inode.log. If that looks OK, check init.sh and the test script itself. You can use make -n to figure out how the test script is being invoked. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?56831> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/