------- Comment #19 from howarth at nitro dot med dot uc dot edu 2009-09-01
04:00 -------
Actually comment 14 has it backwards. If we implement the config.guess
correction so that the host reports the default code generation and execution
as x86_64-apple-darwin*, we would need something like...
Index: configure.ac
===================================================================
--- configure.ac (revision 151196)
+++ configure.ac (working copy)
@@ -1015,6 +1015,12 @@
i[[3456789]]86-*-sysv5*)
host_makefile_frag="config/mh-sysv5"
;;
+ x86_64-*-darwin*)
+ # gcc can default to x86_64 code generation, avoid that
+ if test "${build}" != "${host}"; then
+ tentative_cc="${CC-gcc} -m32"
+ fi
+ ;;
i[[3456789]]86-*-dgux*)
tentative_cc="gcc -Wall -ansi -D__using_DGUX"
host_makefile_frag="config/mh-dgux386"
instead. However this wouldn't be robust enough since if you only passed
--target=x86_64-apple-darwin10, it would trigger the -m32 usage since the
default triplet gets picked up as x86_64-apple-darwin10.0.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41180
