Follow-up Comment #13, bug #63307 (project make): When SIGPIPE is set to the default action, then yes, writing to a closed pipe is expected to get make to die abnormally. That's how SIGPIPE is designed to work. :) This is different from a regular failure to write to stdout.
There is little benefit to continuing the build in that case: if the build continues, spawned processes will see the same closed pipe that make saw, and those spawned processes will likely fail anyway because they too would be terminated by SIGPIPE if they attempt to write to stdout. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63307> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/