On Sun, Jan 24, 2010 at 08:26:04PM -0500, Olexa Bilaniuk wrote:
>
> I am on Mac OS X Snow Leopard. There has been some noise around the
> forums that GCC fails for various reasons. It turns out that despite
> having all the requirements to run 64-bit systems, including a 64-bit
> processor (an Intel Core 2 Duo), no Macs boot the 64-bit kernel by
> default and only 4 (These being Mac Pros, Xserves, Macbook Pros and
> iMacs) are allowed to boot i...@all, leaving that the system kernel
> runs 32-bit, but almost every application is 64-bit. Also, the command
> uname returns i386 despite the Core 2 Duo being more of a i686 or
> x86_64, a 64-bit processor. It seems therefore that config.guess
> confuses itself in bitness, picking the 32-bit version called i386
> rather than the correct choice, x86_64. So the recommendation is to
> add an entry under Build Stats saying that 4.4.3 under
> x86_64-apple-darwin10.2.0 is successful, and to add to the
> system-specific installation notes to add these options to the
> configure:
>
> --host=x86_64-apple-darwin10 --target=x86_64-apple-darwin10
> --host=x86_64-apple-darwin10
>
This issue doesn't exist in either gcc 4.4.3 or gcc trunk as
both contain the updated config.guess which properly detects
the code generation of the default system compiler rather than
using uname for obtaining the architecture. Thus on a EMT64
compatible processor config.guess will return...
x86_64-apple-darwin10.2.0
for the default compiler but if you set CC to gcc-4.0, it will
return...
i386-apple-darwin10.2.0
Jack
