From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: handa@m17n.org, emacs-devel@gnu.org
Subject: Re: [patch] leim/Makefile.in: make distclean should make clean
Date: Mon, 16 Feb 2004 21:54:30 +0200 [thread overview]
Message-ID: <216-Mon16Feb2004215430+0200-eliz@elta.co.il> (raw)
In-Reply-To: <1076951222.4030f8b6a47af@imp2-q.free.fr> (message from Jérôme Marant on Mon, 16 Feb 2004 18:07:02 +0100)
> Date: Mon, 16 Feb 2004 18:07:02 +0100
> From: =?iso-8859-1?b?Suly9G1l?= Marant <jmarant@free.fr>
>
> I'm currently working on an emacs-snapshot Debian package
> which will make us easier to prepare upcoming stable releases
> and to find problems with the build system ASAP.
>
> I'm building it from a tarball I do generate from make-dist
> and every time I clean the package, I remove .elc files
> as well as autogenerated .el ones.
I think this warrants a special target to remove all *.elc files.
The situation you describe is pretty much special.
> There is a rationale for removing them: we usually apply
> patches (which may modify .el files) prior to bootstrapping
> emacs, so we need to regenerate them anyway.
That doesn't require to remove them first: Make will DTRT when it sees
that the corresponding *.el files changed, and will compile only those
which are in the need.
next prev parent reply other threads:[~2004-02-16 19:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-15 19:15 [patch] leim/Makefile.in: make distclean should make clean Jérôme Marant
2004-02-15 23:35 ` Kenichi Handa
2004-02-16 9:39 ` Eli Zaretskii
2004-02-16 11:42 ` Kenichi Handa
2004-02-16 16:25 ` Eli Zaretskii
2004-02-16 16:57 ` Stefan Monnier
2004-02-16 23:25 ` Kenichi Handa
2004-02-17 0:44 ` Stefan Monnier
2004-02-16 12:37 ` Jérôme Marant
2004-02-16 14:39 ` Stefan Monnier
2004-02-16 16:54 ` Jérôme Marant
2004-02-16 16:13 ` Eli Zaretskii
2004-02-16 17:07 ` Jérôme Marant
2004-02-16 19:54 ` Eli Zaretskii [this message]
2004-02-16 21:28 ` Jérôme Marant
2004-02-16 21:51 ` Jérôme Marant
2004-02-17 7:00 ` Eli Zaretskii
2004-02-17 8:13 ` Jérôme Marant
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=216-Mon16Feb2004215430+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).