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.
