From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lute Kamstra Newsgroups: gmane.emacs.devel Subject: Re: Bootstrap problem. Date: Thu, 07 Apr 2005 19:43:51 +0200 Message-ID: <87sm22cwiw.fsf@xs4all.nl> References: <87u0mtsesh.fsf@xs4all.nl> <87br91bbva.fsf@xs4all.nl> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1112895926 9652 80.91.229.2 (7 Apr 2005 17:45:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 7 Apr 2005 17:45:26 +0000 (UTC) Cc: "Kim F. Storm" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 07 19:45:23 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DJb31-0004Iu-AK for ged-emacs-devel@m.gmane.org; Thu, 07 Apr 2005 19:44:08 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DJacM-0003mc-Hq for ged-emacs-devel@m.gmane.org; Thu, 07 Apr 2005 13:16:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DJabw-0003dp-3X for emacs-devel@gnu.org; Thu, 07 Apr 2005 13:16:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DJabt-0003c6-QW for emacs-devel@gnu.org; Thu, 07 Apr 2005 13:16:06 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DJabt-0003b7-1A for emacs-devel@gnu.org; Thu, 07 Apr 2005 13:16:05 -0400 Original-Received: from [194.109.24.22] (helo=smtp-vbr2.xs4all.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DJb3e-0000Sg-9f for emacs-devel@gnu.org; Thu, 07 Apr 2005 13:44:46 -0400 Original-Received: from pijl (a80-127-67-124.adsl.xs4all.nl [80.127.67.124]) by smtp-vbr2.xs4all.nl (8.12.11/8.12.11) with ESMTP id j37Hhx0b013434; Thu, 7 Apr 2005 19:44:00 +0200 (CEST) (envelope-from Lute.Kamstra@xs4all.nl) Original-Received: from lute by pijl with local (Exim 3.36 #1 (Debian)) id 1DJb2o-0005Uc-00; Thu, 07 Apr 2005 19:43:54 +0200 Original-To: emacs-devel@gnu.org In-Reply-To: <87br91bbva.fsf@xs4all.nl> (Lute Kamstra's message of "Wed, 30 Mar 2005 13:40:25 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) Original-Lines: 41 X-Virus-Scanned: by XS4ALL Virus Scanner X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:35702 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:35702 Lute Kamstra writes: > Lute Kamstra writes: > >> Add a definition to lisp file A and make it available to other lisp >> files by adding an autoload cookie. Commit the change. Then add >> some code to lisp file B that depends on the presence of this >> definition to compile. Commit this change as well. >> >> As I found out the hard way, this leads to problems in two cases: > > [...] > >> 2. Someone has a CVS tree and did the last update before the change in >> file A. Then that person does per next update after the change to >> file B and then does a make bootstrap. bootstrap-emacs uses the >> old loaddefs.el that does not contain an autoload of the required >> definition in file A and fails to compile file B. >> >> A second make bootstrap would work fine as this would use the new >> loaddefs.el that was created during the first make bootstrap that >> failed. > > Strange: I just looked more carefully at the bootstrap process and it > seems that this second problem should not occur. From what I now > understand, bootstrap already does what I want: it first updates > loaddefs.el and then builds bootstrap-emacs and dumps it with the > up-to-date loaddefs.el loaded. > > But now I don't know how to explain Chris Moore's recent bug report on > emacs-pretest-bug. I figured it out: a make clean deletes the emacs executable, but not loaddefs.el. So a subsequent make bootstrap cannot use the old emacs to regenerate loaddefs.el and bootstrap-emacs uses the old loaddefs.el to compile the new lisp files. We could let make clean delete loaddefs.el as well. Or would that have any negative effects that I'm not aware of? Lute.