------- Comment #9 from howarth at nitro dot med dot uc dot edu 2009-12-29 23:37 ------- (In reply to comment #8) > --build=xxx means you're using a xxx compiler to build. Since you apparently > don't have a x86_64 compiler at hand but only a i386, you cannot do that. > > You first need to build a i386 -> x86-64 cross-compiler (--host=i386-apple-* > --target=x86_64-apple-*) with the base i386 compiler and then use the > resulting > compiler to build a native x86-64 compiler (--build=x86_64-apple-*). >
Again, it is important to actually check the code generation of the system compiler. On a MacBook Pro with an EMT64 compatible processor, I get... gcc -v Using built-in specs. Target: i686-apple-darwin10 Configured with: /var/tmp/gcc/gcc-5646.1~2/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 Thread model: posix gcc version 4.2.1 (Apple Inc. build 5646) (dot 1) even though this compiler default to x86_64 code generation on this hardware. One of the oddities of a fat binary compiler in Snow Leopard. The reported specs don't match the actual compiler code in use. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42518
