From: Bill Wohler <wohler@newt.com>
To: emacs-devel@gnu.org
Subject: Re: Makefile bug in generating mh-loaddefs.el?
Date: Tue, 03 Jul 2007 21:44:56 -0700 [thread overview]
Message-ID: <87y7hwg4l3.fsf@olgas.newt.com> (raw)
In-Reply-To: uejjoluwy.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Dan Nicolaescu <dann@ics.uci.edu>
>> Date: Tue, 03 Jul 2007 13:55:24 -0700
>> Cc: emacs-devel@gnu.org
>>
>> Do this
>>
>> rm src/emacs mh-e/mh-loaddefs.el
>> cd lisp
>> make mh-autoloads
>>
>> "make mh-autoloads" will fail, now run "make mh-autoloads" again and it will
>> succeed...
>
> I think this is true for almost any other target in lisp/Makefile.
I agree with Eli. The mh-loaddefs.el rule is essentially a copy of the
loaddefs.el rule. If the mh-loaddefs.el rule needs to be fixed, all of
the rules need to be fixed.
> 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.
I'm not sure I'd agree with this practice. If the command fails, the
remnants of the target file could be used for troubleshooting.
Tom's approach--writing to a temporary file and moving it at the
end--seems to answer all issues.
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
next prev parent reply other threads:[~2007-07-04 4:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 18:42 Makefile bug in generating mh-loaddefs.el? Dan Nicolaescu
2007-07-03 20:00 ` Eli Zaretskii
2007-07-03 20:14 ` David Kastrup
2007-07-03 20:25 ` Tom Tromey
2007-07-03 20:55 ` Dan Nicolaescu
2007-07-04 3:17 ` Eli Zaretskii
2007-07-04 4:44 ` Bill Wohler [this message]
2007-07-04 6:21 ` David Kastrup
2007-07-04 8:46 ` Stephen J. Turnbull
2007-07-04 14:16 ` Tom Tromey
2007-07-04 14:19 ` Tom Tromey
2007-07-04 21:25 ` Eli Zaretskii
2007-07-04 23:06 ` David Robinow
2007-07-05 3:28 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y7hwg4l3.fsf@olgas.newt.com \
--to=wohler@newt.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).