From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: stale lisp/Makefile
Date: Thu, 27 Mar 2008 15:15:15 -0400 [thread overview]
Message-ID: <tzk5jo3rng.fsf@fencepost.gnu.org> (raw)
There have been quite a few spurious problems recently reported by
people whose lisp/Makefile is out-of-date with respect to
lisp/Makefile.in.
Personally, I always use `make maintainer-clean; make bootstrap', so I
don't run into these issues, but this seems to be too slow, or
overkill, for some.
Two questions:
1) Have I missed something in my treatment of cal-loaddefs.el etc in
lisp/Makefile.in?
2) Is it possible to add/worth adding a check for an out-of-date
lisp/Makefile? Is this as simple as adding `$(lispdir)/Makefile.in' to
the existing dependency of Makefile on $(srcdir)/Makefile.in in the
top-level Makefile.in?
TIA.
next reply other threads:[~2008-03-27 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 19:15 Glenn Morris [this message]
2008-03-28 9:59 ` stale lisp/Makefile Andreas Schwab
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=tzk5jo3rng.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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).