From: Dan Nicolaescu <dann@ics.uci.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: dump (temacs) fails, core in alloc.c
Date: Mon, 9 Nov 2009 12:37:53 -0800 (PST) [thread overview]
Message-ID: <200911092037.nA9Kbr9u001441@godzilla.ics.uci.edu> (raw)
In-Reply-To: <83zl6vo57i.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Nov 2009 21:42:25 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > Date: Mon, 9 Nov 2009 11:12:05 -0800 (PST)
> > From: Dan Nicolaescu <dann@ics.uci.edu>
> > Cc: Emacs-Devel <emacs-devel@gnu.org>
> >
> > lisp.h is not consistenly listed as a dependency in Makefile (not sure why).
>
> Richard used to be opposed to that, to avoid recompiling everything
> whenever some small part or even comment in lisp.h changes. Not sure
> if this is still a valid concern, what with today's compilation speed.
>
> > So it's probably Stefan's lisp.h change that probably tripped you...
>
> I always manually delete all *.o files when there's a significant
> change in lisp.h.
Tools are much more reliable than humans, compilation speed for emacs is
not a big concern anymore, so IMHO lisp.h should be added as a
dependency.
next prev parent reply other threads:[~2009-11-09 20:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 17:59 dump (temacs) fails, core in alloc.c Jan Djärv
2009-11-09 18:36 ` Jan Djärv
2009-11-09 19:12 ` Dan Nicolaescu
2009-11-09 19:42 ` Eli Zaretskii
2009-11-09 20:37 ` Dan Nicolaescu [this message]
2009-11-09 22:02 ` Stefan Monnier
2009-11-09 23:15 ` Dan Nicolaescu
2009-11-10 14:01 ` Stefan Monnier
2009-11-10 7:07 ` Jan D.
2009-11-10 14:02 ` Stefan Monnier
2009-11-14 15:24 ` Gcc-generated dependencise. (Was: Re: dump (temacs) fails, core in alloc.c) Jan Djärv
2009-11-10 14:56 ` dump (temacs) fails, core in alloc.c Richard Stallman
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=200911092037.nA9Kbr9u001441@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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).