From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Giorgos Keramidas Newsgroups: gmane.emacs.devel Subject: Re: bootstrap failed Date: Thu, 23 Feb 2006 14:27:30 +0200 Message-ID: <20060223122730.GA32722@flame.pc> References: <20060222105741.GA16886@emacsfans.org> <20060223114149.GA29887@flame.pc> <87u0aqw9mj.fsf@emacsfans.tsinghua.edu.cn> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1140832160 20216 80.91.229.2 (25 Feb 2006 01:49:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 25 Feb 2006 01:49:20 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 25 02:49:16 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FCoYc-0007w0-DT for ged-emacs-devel@m.gmane.org; Sat, 25 Feb 2006 02:49:14 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FCoYb-0007Sr-3S for ged-emacs-devel@m.gmane.org; Fri, 24 Feb 2006 20:49:13 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FCWUD-0005tr-7I for emacs-devel@gnu.org; Fri, 24 Feb 2006 01:31:29 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FCWU9-0005rj-O5 for emacs-devel@gnu.org; Fri, 24 Feb 2006 01:31:27 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FCFZt-00050h-4s for emacs-devel@gnu.org; Thu, 23 Feb 2006 07:28:16 -0500 Original-Received: from [62.1.205.36] (helo=igloo.linux.gr) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FCFga-0007og-EL for emacs-devel@gnu.org; Thu, 23 Feb 2006 07:35:08 -0500 Original-Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.5/8.13.5/Debian-3) with ESMTP id k1NCRsHo020658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Feb 2006 14:27:56 +0200 Original-Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id k1NCRU81032727; Thu, 23 Feb 2006 14:27:30 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Original-Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id k1NCRUAA032726; Thu, 23 Feb 2006 14:27:30 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Original-To: Zhang Wei Content-Disposition: inline In-Reply-To: <87u0aqw9mj.fsf@emacsfans.tsinghua.edu.cn> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.367, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.83, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr 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:50915 Archived-At: On 2006-02-23 20:19, Zhang Wei wrote: > Giorgos Keramidas writes: >> Is this from a clean checkout? I've reinstalled Emacs this morning from >> CVS with -D '2006/02/23 07:40:25 UTC' being the last change that went in. >> >> No problems seen here. Can you tell us more of your build environment, >> the compiler you used, any interesting options, etc.? >> > > Yes it was a clean checkout. I just installed debian on a new box, and > build emacs with the following command: > > # apt-get build-dep emacs-snapshot > # cd emacs-cvs > # ./configure CFLAGS=-g --with-gtk && make bootstrap > > # gcc --version > gcc (GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5) > Copyright (C) 2005 Free Software Foundation, Inc. > > After the bootstrap failure, I've installed some other packages. Then > bootstrap again and succeed. No problems now. The problem has gone. I > googled for the error message and found the same problem has been > reproted before. It's a quite strange problem. I'm not sure what apt-get fetches, so I can't help you there. I usually check out the sources from CVS. What you saw may be a problem that is caused by practically anything from the time something is committed, until apt-get downloads its :-/