[mercury-users] [OT] Building gcc-4.1 for Mac?

doug.auclair at logicaltypes.com doug.auclair at logicaltypes.com
Tue Oct 10 12:01:13 AEST 2006


Hm, mgnuc --verbose isn't much help:

../scripts/mgnuc --verbose --grade reg.gc      --c-debug --no-ansi   --       -c mercury_builtin_types.c -o mercury_builtin_types.o
/usr/bin/gcc-3.3 -Wall -Wwrite-strings -Wshadow -Wstrict-prototypes -Wmissing-prototypes -Wno-unused -Wno-uninitialized -O2 -fomit-frame-pointer -DMR_USE_GCC_GLOBAL_REGISTERS -fno-builtin -fno-omit-frame-pointer -DMR_CONSERVATIVE_GC -DMR_BOEHM_GC -D__EXTENSIONS__ -D_GNU_SOURCE -g -fno-loop-optimize -I../boehm_gc -I../boehm_gc/include -DMERCURY_BOOTSTRAP_H -DMERCURY_CONF_BOOTSTRAP_H -c mercury_builtin_types.c -o mercury_builtin_types.o
cc1: warning: command line option "-fobjc-exceptions" is valid for ObjC/ObjC++ but not for C
cc1: error: unrecognized command line option "-fconstant-cfstrings"
make[2]: *** [mercury_builtin_types.o] Error 1
make[1]: *** [runtime] Error 2
make: *** [all] Error 2

Does this verbose output provide any clues?  Is there some environment that I should
be setting externally (like, I don't know, maybe, GCC_HOME or some such)?

I did compile gcc-4.1.1, but it complains (and dies) when trying to link .s files (assembly language),
so it appears that the FSF may not have full compatibility for intel macs for gcc-4.1.1 yet ...

Sincerely,
Doug Auclair

--------------------------------------------------------------------------
mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the users mailing list