New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
find: unrecognized: -execdir PR buildconf: use find -execdir / busybox find #5483
Comments
form the logs: find: unrecognized: -execdir BusyBox v1.31.1 () multi-call binary. Usage: find [-HL] [PATH]... [OPTIONS] [ACTIONS] Search for files and perform actions on them. First failed action stops processing of current file. Defaults: PATH is current directory, action is '-print'
Actions:
If none of the following actions is specified, -print is assumed
find: unrecognized: -execdir BusyBox v1.31.1 () multi-call binary. |
Can you just check? No, travis shows no errors. Presumably it doesn't use busybox's find. I don't understand why someone would do that for development. |
In most cases that is a fairly benign problem too. |
with a manual make build with/in the curl-docker its the same problem |
after the commit (c712009)
the build fails and/or generate lots of errors.
as the busybox find dont support -execdir
travis build errors
With these errors: the travis runs should show an error message, shouldn't they?
The text was updated successfully, but these errors were encountered: