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. You >> 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.
