From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Bruce Hoglund <bhoglund@mac.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: long long size compute failure during make of gcc-4.6.1 on OS X 10.7 Lion
Date: Wed, 07 Sep 2011 08:30:00 -0000 [thread overview]
Message-ID: <CAH6eHdTNV7cuM+snwAkCZ79hRoFs_XPzo=0Bmn5GGUi0niskMA@mail.gmail.com> (raw)
In-Reply-To: <563FFE3F-C083-4668-B459-EF4D00E4EECB@mac.com>
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"
next prev parent reply other threads:[~2011-09-07 8:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 21:22 Bruce Hoglund
2011-09-06 21:52 ` Jonathan Wakely
2011-09-07 1:48 ` Bruce Hoglund
2011-09-07 5:06 ` Ian Lance Taylor
2011-09-07 8:28 ` Jonathan Wakely
2011-09-07 13:53 ` Bruce Hoglund
2011-09-07 14:02 ` Jonathan Wakely
2011-09-07 15:26 ` Bruce Hoglund
2011-09-07 15:42 ` Jonathan Wakely
2011-09-07 15:50 ` Jonathan Wakely
2011-09-07 13:49 ` Bruce Hoglund
2011-09-07 14:07 ` Jonathan Wakely
2011-09-07 15:35 ` Bruce Hoglund
2011-09-07 16:32 ` Ian Lance Taylor
2011-09-07 22:11 ` Bruce Hoglund
2011-09-09 16:18 ` Jonathan Wakely
2011-09-09 20:40 ` Bruce Hoglund
2011-09-07 15:48 ` Ian Lance Taylor
2011-09-07 8:30 ` Jonathan Wakely [this message]
[not found] ` <37D86901-9803-45C7-B143-CC9A7D3E8814@mac.com>
2011-09-07 15:45 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdTNV7cuM+snwAkCZ79hRoFs_XPzo=0Bmn5GGUi0niskMA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=bhoglund@mac.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).