unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: ldefs-boot.el
Date: Sat, 13 Aug 2005 19:30:32 -0500 (CDT)	[thread overview]
Message-ID: <200508140030.j7E0UWT12396@raven.dms.auburn.edu> (raw)
In-Reply-To: <jkoe82iquv.fsf@glug.org> (message from Thien-Thi Nguyen on 12 Aug 2005 21:10:32 -0400)

Thien-Thi Nguyen wrote:

   > # bootstrap should always work with ldefs-boot.el.
   > 
   > No, it does not always work.  (How could it?)  It only works if you
   > update ldefs-boot whenever needed.

   the "should" in the last sentence of the makefile frag implies the last
   sentence you wrote ("it only works...").  perhaps adding that sentence to
   the makefile would be sufficient to nudge the implication to explanation?

I suggest the following exoansion of the comment in lisp/Makefile.in.
I can install if it looks OK.

===File ~/lisp-Makefile.in-diff=============================
*** Makefile.in	07 Aug 2005 10:23:06 -0500	1.65
--- Makefile.in	13 Aug 2005 18:29:24 -0500	
***************
*** 218,227 ****
  # Build loaddefs.el to make sure it's up-to-date.  If it's not, that
  # might lead to errors during the bootstrap because something fails to
  # autoload as expected.  If there is no emacs binary, then we can't
! # build autoloads yet.  In that case we have to use ldefs-boot.el;
! # bootstrap should always work with ldefs-boot.el.  (Because
! # loaddefs.el is an automatically generated file, we don't want to
! # store it in the source repository).
  
  bootstrap-prepare:
  	if test -x $(EMACS); then				\
--- 218,230 ----
  # Build loaddefs.el to make sure it's up-to-date.  If it's not, that
  # might lead to errors during the bootstrap because something fails to
  # autoload as expected.  If there is no emacs binary, then we can't
! # build autoloads yet.  In that case we have to use ldefs-boot.el.
! # Bootstrap should always work with ldefs-boot.el.  Therefore,
! # whenever a new autoload cookie gets added that is necessary during
! # bootstrapping, ldefs-boot.el should be updated by overwriting it with
! # an up-to-date copy of loaddefs.el that is uncorrupted by
! # local changes.  (Because loaddefs.el is an automatically generated
! # file, we don't want to store it in the source repository).
  
  bootstrap-prepare:
  	if test -x $(EMACS); then				\
============================================================

  reply	other threads:[~2005-08-14  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 19:49 ldefs-boot.el Luc Teirlinck
2005-08-13  1:10 ` ldefs-boot.el Thien-Thi Nguyen
2005-08-14  0:30   ` Luc Teirlinck [this message]
2005-08-14  0:35   ` ldefs-boot.el Luc Teirlinck
2005-08-14  9:49     ` ldefs-boot.el Thien-Thi Nguyen
2005-08-13 14:40 ` ldefs-boot.el Richard M. Stallman

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=200508140030.j7E0UWT12396@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).