When we setup a command to run, e.g. $FOO we typically set this to just a path to a binary, e.g. /usr/bin/foo. However, this is not necessarily true. On Windows, this can be prefixed by the $FIXPATH prefix, and on all platforms we are allowed to pass arguments to the executable.
If we want to test if this binary actually exists, we need to extract the binary name from this command line. We have a NOFIXPATH argument to UTIL_LOOKUP_PROGS, which tried to resolve this, but it is not enough, and it makes it impossible to both lookup a program properly and also check for its existance afterwards. Instead, I propose to add a UTIL_GET_EXECUTABLE function that extracts just the path to the binary from such a command. ------------- Commit messages: - 8356379: Need a proper way to test existence of binary from configure Changes: https://git.openjdk.org/jdk/pull/25087/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=25087&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8356379 Stats: 37 lines in 2 files changed: 20 ins; 8 del; 9 mod Patch: https://git.openjdk.org/jdk/pull/25087.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/25087/head:pull/25087 PR: https://git.openjdk.org/jdk/pull/25087
