-
Notifications
You must be signed in to change notification settings - Fork 30
Make the configure script fail on command failures #101
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
base: master
Are you sure you want to change the base?
Conversation
04a44cf to
8e0ff16
Compare
|
I wonder why we have to consider ancient implementations like MSYS2 that never got updated. If you want a working build system on Windows, run a Linux shell. It's all there. |
8e0ff16 to
0211a88
Compare
|
Arf sorry my bad, i worked from (flawed) memory and didn't bother to double-check what i was saying. Sorry again. I removed that change, however the first commit about hardening the script against failures would be greatly appreciated. I think what happened with the failure on msys2 (from someone i was helping get things working) was that |
|
Out of curiosity to check what else may be going on, where did the problem originally arise? It sounds like the original issue was a user's |
yes, i believe the user had their MSYS2 path after However i think this PR is desirable regardless of what opam does |
'find -exec cmd {} ;' will call cmd for each file, however if the command has a non-zero exit code find will simply ignore the error code and continue as if nothing happened. Piping into read is much simply at the cost of not supporting filenames containing \n but ocamlfind doesn't have any and extremely unlikely thing to happen so this is safe to do.
|
I had to debug yet another issue where ocamlfind simply ignored a segfault and continued the installation as if nothing happened resulting in a broken installation. This time the problem of the user was that they were using |
|
Any chance this could be merged? Users keep hitting this issue |
The added
set -eis here to harden the script and make sure such failures are caught early. Otherwise the script will simply ignore failing commands and carry on.