From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-185186-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 29237 invoked by alias); 4 Jan 2007 16:34:40 -0000
Received: (qmail 29102 invoked by uid 22791); 4 Jan 2007 16:34:38 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)     by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 04 Jan 2007 16:34:28 +0000
Received: from drow by nevyn.them.org with local (Exim 4.63) 	(envelope-from <drow@nevyn.them.org>) 	id 1H2VXt-00055M-M8; Thu, 04 Jan 2007 11:34:25 -0500
Date: Thu, 04 Jan 2007 16:34:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Marcin Dalecki <martin@dalecki.de>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: libgcc move to the top level
Message-ID: <20070104163425.GA19488@nevyn.them.org>
Mail-Followup-To: Marcin Dalecki <martin@dalecki.de>, 	gcc-patches List <gcc-patches@gcc.gnu.org>
References: <20061229180139.GA16625@nevyn.them.org> <45962160.40707@lu.unisi.ch> <20061230201926.GA25399@nevyn.them.org> <4597DEB7.90900@lu.unisi.ch> <20061231195643.GA24283@nevyn.them.org> <jed55vezvv.fsf@sykes.suse.de> <20070104140534.GA15103@nevyn.them.org> <B843F012-0D22-41A2-8917-D6F51A59A15B@dalecki.de> <20070104150149.GA17084@nevyn.them.org> <6FE472E8-307C-4FD8-8B34-BD8016812338@dalecki.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6FE472E8-307C-4FD8-8B34-BD8016812338@dalecki.de>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-IsSubscribed: yes
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
X-SW-Source: 2007-01/txt/msg00246.txt.bz2

On Thu, Jan 04, 2007 at 05:13:07PM +0100, Marcin Dalecki wrote:
> Using a separate objdir appears to work. However the build process
> doesn't stop after actually having build GCC. The whole (pretty
> pointless, since it's mixing testing with building, if you ask) stage
> fun starts (Yes! Burn fossil energy. Burn!). Apparently
> --disable-bootstrap got just ignored without being even diagnosed.

If you can post logs of what's going on, without insults mixed in, I'll
look at them.  --disable-bootstrap works fine for me as of this
morning.

-- 
Daniel Jacobowitz
CodeSourcery