-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
setup-hooks: do not pass missing dirs to find #15405
Conversation
By analyzing the blame information on this pull request, we identified @edolstra to be a potential reviewer |
Alternatively we might opt not to even run |
These returns are bad, as the exit code of the last command is used which means failure. We need
|
Well, in this particular case the problem is |
find fails when called with an inexistent search path. That situation may arise when the output is created after by a postFixup hook.
Updated this PR to fix the calls to return. Same restrictions as the update in #15339. |
find fails when called with an inexistent search path. That situation may arise when the output is created after by a postFixup hook. vcunat amended the PR by clarifying one more `return` to `return 0`.
Thanks. Staged with clarifying one more |
Thanks for following and improving this PR :-) Le 22 mai 2016 12:18:26 UTC+02:00, "Vladimír Čunát" notifications@github.com a écrit :
|
:-) |
find
fails when called with an inexistent search path.That situation may arise when the output is created after by a postFixup hook.
I discovered the bug while building the nss package for #15339.
In that case, the "tools" output is only creted in the postFixup hook by the
moveToOutput bin "$tools"
here.More generally, the multiple output features increases the risk to encounter empty or missing prefixes during the build.
The issue was introduced by a refactoring in d71a485.
This PR fixes my comment on that commit. (here)