From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14368 invoked by alias); 7 Sep 2011 08:30:47 -0000 Received: (qmail 14293 invoked by uid 22791); 7 Sep 2011 08:30:42 -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-pz0-f49.google.com (HELO mail-pz0-f49.google.com) (209.85.210.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 07 Sep 2011 08:30:29 +0000 Received: by pzk6 with SMTP id 6so15114352pzk.8 for ; Wed, 07 Sep 2011 01:30:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.5.169 with SMTP id t9mr15103pbt.324.1315384228589; Wed, 07 Sep 2011 01:30:28 -0700 (PDT) Received: by 10.142.90.10 with HTTP; Wed, 7 Sep 2011 01:30:28 -0700 (PDT) In-Reply-To: <563FFE3F-C083-4668-B459-EF4D00E4EECB@mac.com> References: <76A9B64F-3A3E-451E-BC23-EB4580B9875F@mac.com> <563FFE3F-C083-4668-B459-EF4D00E4EECB@mac.com> Date: Wed, 07 Sep 2011 08:30: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: gcc-help@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 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/msg00050.txt.bz2 On 7 September 2011 02:48, Bruce Hoglund wrote: > On Sep 6, 2011, at 5:52 PM, Jonathan Wakely wrote: > >> On 6 September 2011 22:22, Bruce Hoglund wrote: >>> >>> See `config.log' for more details. >> >> Try this. > > > Alright Professor Dumbledore, I mean Professor Wakely, your subtle pointing out which magical things I'm to notice is lost on me. I'm a bit dense on the config.log as I haven't a clue as to what a normal one looks like! Is it magic to know that an error message saying "Cannot do blahblah. See X for more details" indicates you should see X for more details of what went wrong? And searching for "Cannot do blahblah" would probably get you to the right location in the file. I didn't say "read and understand the whole of config.log"