From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: "make" in lisp/ not doing The Right Thing?
Date: Wed, 20 Feb 2002 16:03:47 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0202201559370.3725-100000@yxa.extundo.com> (raw)
In-Reply-To: <87sn7w1aah.fsf@cs.utah.edu>
On Wed, 20 Feb 2002, Karra wrote:
> Is there any good reason for the following behaviour: _all_ .elc
> files are built from the .el files, even if they are newer than the
> corresponding .el files.
Yes. Some files contain macros used by other files. If the macro is
changed, the other file need to be compiled as well. Maybe someone can
write a makefile dependency generator for elisp, but there isn't one
AFAIK.
Type "make l" if you know the code well enough to feel confident about
only compiling updated lisp files. This is why a ding.cvs-patches
newsgroup or similar would be useful, btw.
next prev parent reply other threads:[~2002-02-20 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 14:45 Karra
2002-02-20 15:03 ` Simon Josefsson [this message]
2002-02-20 15:03 ` Simon Josefsson
2002-02-20 15:15 ` ShengHuo ZHU
2002-02-20 15:15 ` ShengHuo ZHU
2002-02-20 15:23 ` ShengHuo ZHU
2002-02-20 15:23 ` ShengHuo ZHU
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 14:45 Karra
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0202201559370.3725-100000@yxa.extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.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 NNTP newsgroup(s).