public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
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 14:02:00 -0000	[thread overview]
Message-ID: <CAH6eHdTAyx2ZcBsBHW5Jiwdnqe0NQ+ePGMxD6CbQxRxsG8RFww@mail.gmail.com> (raw)
In-Reply-To: <6A491C25-3199-49FA-A2A1-447CD041148F@mac.com>

On 7 September 2011 14:52, Bruce Hoglund wrote:
>
> On Sep 7, 2011, at 4:27 AM, Jonathan Wakely wrote:
>
>> On 7 September 2011 06:06, Ian Lance Taylor wrote:
>>> This is probably the wrong config.log file.  You need the one in the
>>> directory in which configure is being run.  In this case,
>>> gcc/config.log.
>>>
>>> In general, the bottommost parts of config.log are not helpful.  You
>>> need to look for the failing test.
>>
>> Which to remind you, was:
>> configure: error: cannot compute sizeof (long long)
>
>
> Yes, thank you.
>
> I simplistically searched for the string "long" & it was not found in the config.log. As a guess, I'd say the failure to compute the size of the long long was a collateral damage effect from some other failure, such as the one I sent Ian:

No, you looked in the wrong config.log

As Ian said, you need to look for config.log in the directory where
configure is being run, that is NOT necessarily the directory where
YOU ran configure.  When you run the top-level configure it
recursively runs configure scripts in sub-directories.  One of those
failed.

In your case it says there is an error in /Users/bhoglund/tmp/gcc46/gcc:

checking size of long long... configure: error: in
`/Users/bhoglund/tmp/gcc46/gcc':
configure: error: cannot compute sizeof (long long)
See `config.log' for more details.

So that's the directory where you need to look in config.log, which as
Ian said is gcc/config.log

Look in there, you will find the "cannot compute sizeof (long long)"
error, with more details.

  reply	other threads:[~2011-09-07 14:02 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 [this message]
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
     [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=CAH6eHdTAyx2ZcBsBHW5Jiwdnqe0NQ+ePGMxD6CbQxRxsG8RFww@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).