On 2011-11-14 13:48 , Ryan Schmidt wrote:
On Nov 13, 2011, at 20:33, [email protected] wrote:Revision: 87198 http://trac.macports.org/changeset/87198 Author: [email protected] Date: 2011-11-13 18:33:36 -0800 (Sun, 13 Nov 2011) Log Message: ----------- x11/xorg-libX11 changed configure.compiler (when set to clang) to llvm-gcc-4.2 to avoid UsingTheRightCompiler error on ${configure.cpp}I'm hesitant about that justification. What I don't understand is why doesn't the clang suite contain a preprocessor?
Yeah, that's not a good reason to not use clang. It obviously does contain a preprocessor, accessible via clang -E, but apparently not a separate cpp command. You'd have to ask Apple and/or the LLVM people why that is.
You'd want to check if 'clang -E' is an acceptable value for RAWCPP. If so, we can probably use that as the configure.cpp value for configure.compiler clang. If not, maybe we should use llvm-cpp-4.2, similar to how we use llvm-g++-4.2 on systems where there is no clang++.
- Josh _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
