Try to avoid "find: The environment is too large for exec()" #686
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Followup to #678, which replaced the prior "rename
blah.exe
toblah
" routines with a call tofind -exec ln -s
(symlink instead of rename). However, on Windows distros, this command seems to spuriously fail with the following error:Per
find
docs:Although I am not entirely sure what is causing this error (too many env vars? an env var (probably
PATH
) that is too big?), this PR implements two workarounds to mitigate both possibilities:PATH
using Bash's built-in POSIX extended regex support, andfind
to lookupblah.exe
candidates.An additional check before
ln -s
is included to prevent the following error: