On 2011-2-4 06:57 , James Gregurich wrote: > excuse me. I should quoted the following instead: > > > > |CFLAGS| > Extra flags to give to the C compiler. > |CXXFLAGS| > Extra flags to give to the C++ compiler. > > |CPPFLAGS| > Extra flags to give to the C preprocessor and programs that use it > (the C and Fortran compilers).
I don't see what this is meant to demonstrate. Yes, the preprocessor gets invoked when you compile, so CPPFLAGS get used then as well. Using -arch does change the values of some predefined macros, but anything that relies on that when running the preprocessor on its own is probably broken. This is most apparent when building universal (as demonstrated in the message in the topic). It looks like the expat configure script is (at best) assuming a cross compiling model where you use a differently named toolchain. The fact that the iPhone SDK will try to include some i386-specific headers is kind of weird however you look at it (though understandable given how it was made and intended to be used). - Josh _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
