From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Subject: Re: makefile cruft
Date: Tue, 12 Mar 2002 17:50:37 -0800 [thread overview]
Message-ID: <a6mblc$71i$2@main.gmane.org> (raw)
In-Reply-To: <E16kxaj-0003hr-00@giblet> (message from Thien-Thi Nguyen on Tue, 12 Mar 2002 17:30:09 -0800)
ok, nevermind, i found this in the make info pages:
Usually when a command fails, if it has changed the target file at
all, the file is corrupted and cannot be used--or at least it is not
completely updated. Yet the file's timestamp says that it is now up to
date, so the next time `make' runs, it will not try to update that
file. The situation is just the same as when the command is killed by a
signal; *note Interrupts::. So generally the right thing to do is to
delete the target file if the command fails after beginning to change
the file. `make' will do this if `.DELETE_ON_ERROR' appears as a
target. This is almost always what you want `make' to do, but it is
not historical practice; so for compatibility, you must explicitly
request it.
i suppose when gcc fails it is the one that removes the output file, so
must all applications that want this behavior.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next parent reply other threads:[~2002-03-13 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16kxaj-0003hr-00@giblet>
2002-03-13 1:50 ` Thien-Thi Nguyen [this message]
2002-03-13 1:30 makefile cruft Thien-Thi Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a6mblc$71i$2@main.gmane.org' \
--to=ttn@giblet.glug.org \
--cc=ttn@glug.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).