* stale lisp/Makefile
@ 2008-03-27 19:15 Glenn Morris
2008-03-28 9:59 ` Andreas Schwab
0 siblings, 1 reply; 2+ messages in thread
From: Glenn Morris @ 2008-03-27 19:15 UTC (permalink / raw)
To: emacs-devel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: stale lisp/Makefile
2008-03-27 19:15 stale lisp/Makefile Glenn Morris
@ 2008-03-28 9:59 ` Andreas Schwab
0 siblings, 0 replies; 2+ messages in thread
From: Andreas Schwab @ 2008-03-28 9:59 UTC (permalink / raw)
To: Glenn Morris; +Cc: emacs-devel
Glenn Morris <rgm@gnu.org> writes:
> 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.
I've checked in a fix.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-03-28 9:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-27 19:15 stale lisp/Makefile Glenn Morris
2008-03-28 9:59 ` Andreas Schwab
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).