unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: generated-autoload-file sometimes not created
Date: Wed, 09 Apr 2008 16:16:14 -0400	[thread overview]
Message-ID: <jwvlk3mhk6b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <q5abk2dfpb.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 09 Apr 2008 14:51:44 -0400")

> I have locally added (rightly, I think) calc/calc-loaddefs.el to
> AUTOGENEL in lisp/Makefile.in.  However, it is not recreated on
> bootstrapping if the timestamp of calc/*.el is older than that of
> loaddefs.el (at least, I think this is what is happening).  I believe
> this indicates a bug in the code that generates autoload files.

Indeed, we have a problem: "make bootstrap" will not recreate all the
autoloads, but only those of the files that are more recent than
ldefs-boot.el.

So I suggest the patch below.  Can someone test it and fix/install it?


        Stefan


Index: lisp/loadup.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/loadup.el,v
retrieving revision 1.162
diff -u -r1.162 loadup.el
--- lisp/loadup.el	9 Apr 2008 03:44:26 -0000	1.162
+++ lisp/loadup.el	9 Apr 2008 20:15:12 -0000
@@ -81,7 +81,13 @@
 (message "Lists of integers (garbage collection statistics) are normal output")
 (message "while building Emacs; they do not indicate a problem.")
 (message "%s" (garbage-collect))
-(load "loaddefs.el")  ;Don't get confused if someone compiled this by mistake.
+
+(condition-case nil
+    ;; Don't get confused if someone compiled this by mistake.
+    (load "loaddefs.el")
+  ;; In case loaddefs hasn't been generated yet.
+  (file-error (load "ldefs-boot.el")))
+
 (message "%s" (garbage-collect))
 (load "simple")
 
Index: lisp/Makefile.in
===================================================================
RCS file: /sources/emacs/emacs/lisp/Makefile.in,v
retrieving revision 1.104
diff -u -r1.104 Makefile.in
--- lisp/Makefile.in	8 Apr 2008 22:12:12 -0000	1.104
+++ lisp/Makefile.in	9 Apr 2008 20:15:12 -0000
@@ -277,11 +277,8 @@
 bootstrap-prepare:
 	if test -x $(EMACS); then				\
 	  $(MAKE) $(MFLAGS) autoloads;				\
-	else							\
-	  cp $(lisp)/ldefs-boot.el $(lisp)/loaddefs.el;		\
 	fi
-	chmod +w $(lisp)/loaddefs.el		\
-	  $(lisp)/ps-print.el			\
+	chmod +w $(lisp)/ps-print.el			\
 	  $(lisp)/emacs-lisp/cl-loaddefs.el
 
 maintainer-clean: distclean bootstrap-clean




  reply	other threads:[~2008-04-09 20:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 18:51 generated-autoload-file sometimes not created Glenn Morris
2008-04-09 20:16 ` Stefan Monnier [this message]
2008-04-10  8:02   ` Mike Mattie
2008-04-10 19:15     ` Stefan Monnier
2008-04-11  3:56   ` Glenn Morris
2008-04-11 16:06     ` Stefan Monnier

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=jwvlk3mhk6b.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).