From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27984 invoked by alias); 7 Sep 2011 14:07:27 -0000 Received: (qmail 27972 invoked by uid 22791); 7 Sep 2011 14:07:25 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-yx0-f175.google.com (HELO mail-yx0-f175.google.com) (209.85.213.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 07 Sep 2011 14:07:10 +0000 Received: by yxl11 with SMTP id 11so3892030yxl.20 for ; Wed, 07 Sep 2011 07:07:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.59.230 with SMTP id c6mr2072618pbr.257.1315404429381; Wed, 07 Sep 2011 07:07:09 -0700 (PDT) Received: by 10.142.90.10 with HTTP; Wed, 7 Sep 2011 07:07:09 -0700 (PDT) In-Reply-To: <9ED5FF3E-92FA-433A-8D09-CE81ABEC238D@mac.com> References: <76A9B64F-3A3E-451E-BC23-EB4580B9875F@mac.com> <563FFE3F-C083-4668-B459-EF4D00E4EECB@mac.com> <9ED5FF3E-92FA-433A-8D09-CE81ABEC238D@mac.com> Date: Wed, 07 Sep 2011 14:07:00 -0000 Message-ID: Subject: Re: long long size compute failure during make of gcc-4.6.1 on OS X 10.7 Lion From: Jonathan Wakely To: Bruce Hoglund Cc: Ian Lance Taylor , gcc-help@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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-09/txt/msg00055.txt.bz2 On 7 September 2011 14:48, Bruce Hoglund wrote: > > On Sep 7, 2011, at 1:06 AM, Ian Lance Taylor wrote: >> >> In general, the bottommost parts of config.log are not helpful. =A0You >> need to look for the failing test. > > Searching the config.log on the word "fail" I found this middle bit: Searching for "fail" in config.log is a total waste of time. Individual tests run by configure are *supposed* to fail, that's how it works. It tries lots of different tests and records the results, so it knows what works on your system and what doesn't. It is by design that many of them fail to compile or execute, configure just keeps going trying other tests unless it hits some fatal error. You need to find the failing test which *isn't* supposed to fail, the "cannot compute sizeof (long long)" one, which is in gcc/config.log - you should ignore all the other failures in that file, just find the one which caused the fatal error that caused your build to fail.