From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.user Subject: Re: makefile cruft Date: Tue, 12 Mar 2002 17:50:37 -0800 Sender: guile-user-admin@gnu.org Message-ID: References: Reply-To: ttn@glug.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1015984620 7218 80.91.224.249 (13 Mar 2002 01:57:00 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 13 Mar 2002 01:57:00 +0000 (UTC) Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16ky0f-0001sJ-00 for ; Wed, 13 Mar 2002 02:56:59 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16kxy7-0000Tm-00; Tue, 12 Mar 2002 20:54:19 -0500 Original-Received: from ca-crlsbd-u3-c5c-122.crlsca.adelphia.net ([68.64.59.122] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16kxx0-0000Qc-00; Tue, 12 Mar 2002 20:53:11 -0500 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16kxuX-0003jh-00; Tue, 12 Mar 2002 17:50:37 -0800 Original-To: guile-devel@gnu.org, guile-user@gnu.org In-Reply-To: (message from Thien-Thi Nguyen on Tue, 12 Mar 2002 17:30:09 -0800) Errors-To: guile-user-admin@gnu.org X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.user:10 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:10 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