From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.devel Subject: Re: Problem with building Emacs diagnosed. Help please! Date: Sat, 09 Aug 2008 01:00:58 +0200 Message-ID: <489CD02A.6060308@gmail.com> References: <20080802101239.GA3890@muc.de> <01ljze53ie.fsf@fencepost.gnu.org> <20080804170517.GA17959@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1218236494 14520 80.91.229.12 (8 Aug 2008 23:01:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Aug 2008 23:01:34 +0000 (UTC) Cc: Alan Mackenzie , emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 09 01:02:25 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KRayV-0002Uh-HX for ged-emacs-devel@m.gmane.org; Sat, 09 Aug 2008 01:02:23 +0200 Original-Received: from localhost ([127.0.0.1]:56616 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KRaxZ-0003rV-HG for ged-emacs-devel@m.gmane.org; Fri, 08 Aug 2008 19:01:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KRaxU-0003qQ-E6 for emacs-devel@gnu.org; Fri, 08 Aug 2008 19:01:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KRaxT-0003oh-2F for emacs-devel@gnu.org; Fri, 08 Aug 2008 19:01:20 -0400 Original-Received: from [199.232.76.173] (port=45578 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KRaxS-0003oZ-PL for emacs-devel@gnu.org; Fri, 08 Aug 2008 19:01:18 -0400 Original-Received: from ch-smtp02.sth.basefarm.net ([80.76.149.213]:52380) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KRaxN-0002Dn-Mf; Fri, 08 Aug 2008 19:01:14 -0400 Original-Received: from c83-254-151-176.bredband.comhem.se ([83.254.151.176]:59441 helo=[127.0.0.1]) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1KRaxL-0007wk-8J; Sat, 09 Aug 2008 01:01:12 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 In-Reply-To: X-Antivirus: avast! (VPS 080808-0, 2008-08-08), Outbound message X-Antivirus-Status: Clean X-Originating-IP: 83.254.151.176 X-Scan-Result: No virus found in message 1KRaxL-0007wk-8J. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1KRaxL-0007wk-8J 7aa021be4a7592301a92d3c5665ead1e X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!) 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:102222 Archived-At: Glenn Morris wrote: > Alan Mackenzie wrote: > >> I am not prepared to check out the sources from scratch every time I >> can't get a build working. > > I didn't mean that. I meant that you seem at the moment to have gotten > into a very weird state somehow, and rather than trying to figure it > out, it would be easier to throw it away and start again. If you get > into the weird state again, then it makes more sense to investigate > it. But for some hopefully transient, never-repeatable glitch, why > bother? > > (Perhaps the "emacs" that your build invokes to make the autoloads is > messed up somehow, or it finds the wrong one somehow.) > > I update and build from CVS every day and almost never see build > failures, and they are always rapidly fixed. I'm sure the same is true > for others. I have a problem right now that I hope is solved, but I am not sure. Since I have quite a lot of patches to Emacs I can't just download the sources again. I tried bootstrap-clean, but it did not seem to help. Now I have manually deleted diary-loaddefs.el (or what it was called). It would be nice if there were a file somewhere in the distribution that explains what to do in strange situations. No need to write it, but every time something stranges pops up and gets solved a note could be added. (Of course the notes must be reviewed now and then to see if they are still valid, but I still think it could save time.)