3 ms·
Once you step off the beaten path, you find that errors from things like: false | true Get silently swallowed by bash (this is configurable, but the default i
by hedora 4y ago
Once you step off the beaten path, you find that errors from things like:
false | true
Get silently swallowed by bash (this is configurable, but the default ignores such errors). Also, the point about not noticing that a rule didn't create its target is a good one. (That behavior should be configurable; I don't think it is.)
Anyway, with -j, make is as async as pretty much anything else out there.
- imoverclocked 4y agoSome targets are virtual and don't create a file named as the target. Sometimes a target may or may not create a file based on internal logic. make itself is consistent in that it looks for errors from return status of the commands it spawns.
- Izkata 4y ago> false | true That statement succeeds. Where's the error? To be more precise... "make" isn't "bash". There's no problem with "make" here and it has no way to see inside bash's internals. It's a bit like asking "make" to understand python, javascript, and java code and runtimes.
- sgtnoodle 4y agoI think the desire would be for that statement to fail. The pipe looks like a logical or, but it's actually for chaining IO. Always a good idea to turn on the pipefail option in your bash scripts.
- Izkata 4y agoYeah, that's what I mean: This is a bash thing, not a make thing - but they're ascribing it to make instead of bash.
- meindnoch 4y agoset -euo pipefail
- bombolo 4y agoYou can set bash to fail on that…