On 14/09/2005, at 5:32 PM, Mike Stump wrote:
These types of rules are not ^C safe:
cc1-checksum.c : cc1-dummy$(exeext) build/genchecksum$(build_exeext)
build/genchecksum$(build_exeext) cc1-dummy$(exeext) $@
It is a general property that builds are ^C safe, the above changes
retard
On Sep 15, 2005, Geoffrey Keating [EMAIL PROTECTED] wrote:
On 14/09/2005, at 5:32 PM, Mike Stump wrote:
If you output to a temp file, and then mv them to the final file,
they will be (I think) safe.
From the 'make' documentation, node 'Interrupts':
If `make' gets a fatal signal while a
On Sep 14, 2005, at 11:55 PM, Geoffrey Keating wrote:
So, I think this is safe.
My build system (GNU make 3.80 on darwin) disagrees with your theory,
I saw two zero length files, created from one -j2 build interrupted
with a normal ^C. I usually never so interrupt builds, so the
These types of rules are not ^C safe:
cc1-checksum.c : cc1-dummy$(exeext) build/genchecksum$(build_exeext)
build/genchecksum$(build_exeext) cc1-dummy$(exeext) $@
It is a general property that builds are ^C safe, the above changes
retard that feature.
If you output to a temp file,
