Reject wrong find utility
Currently our configure scripts try to find the correct find tool on the
However because Windows also has a utility named
find, depending on the user's configuration the Windows one may be on the path first.
The Configure script currently rejects the tool and continues trying to find the correct
find utility from
However the binary distribution script doesn't get to know which find utility to use. So if the wrong
find is on the path then the windows binary downloads will fail with a weird error.
The find utility to use should probably be passed to the tarballs download script. We could just stuff it in an
Env variable and use it in the script if available.