From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17721 invoked by alias); 18 Nov 2011 06:27:45 -0000 Received: (qmail 17706 invoked by uid 22791); 18 Nov 2011 06:27:44 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-iy0-f175.google.com (HELO mail-iy0-f175.google.com) (209.85.210.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Nov 2011 06:27:31 +0000 Received: by iahk25 with SMTP id k25so3505442iah.20 for ; Thu, 17 Nov 2011 22:27:30 -0800 (PST) Received: by 10.42.161.69 with SMTP id s5mr918392icx.23.1321597650474; Thu, 17 Nov 2011 22:27:30 -0800 (PST) Received: by 10.42.161.69 with SMTP id s5mr918378icx.23.1321597650383; Thu, 17 Nov 2011 22:27:30 -0800 (PST) Received: from coign.google.com ([216.239.45.130]) by mx.google.com with ESMTPS id wo4sm26772593igc.5.2011.11.17.22.27.28 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 22:27:29 -0800 (PST) From: Ian Lance Taylor To: Matt Cc: gcc-help@gcc.gnu.org Subject: Re: bootstrap comparison failure with bootstrap-lto References: Date: Fri, 18 Nov 2011 13:47:00 -0000 In-Reply-To: (matt@use.net's message of "Thu, 17 Nov 2011 15:58:36 -0800 (PST)") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-11/txt/msg00178.txt.bz2 Matt writes: > It *kind of* says why. I've pasted the output below. Unfortunately, > when the full build is finished, the prev-gcc/xgcc no longer > exists. When I test the conftest.c (copied and pasted from the log), > the stage1-gcc/xgcc and stage2-gcc/xgcc have no problem with it (of > course). OK, if this works after the build is complete, then you are going to need to stop the build in the middle. Fortunately, this can be done easily enough by running "make configure-stage2-gcc". That should stop after the stage2-gcc directory is configured. At that point, you should see a stage2-gcc directory and a prev-gcc directory. Presumably the stage2-gcc/config.log file will show a failure, and with luck you will be able to recreate that failure at that point. Ian