On Feb 1, 2012, at 10:58, Aljaž Srebrnič wrote: > No, no PortGroup is used, but compiler.cpath solves the issue! > It is strangely undocumented, though… :/
Yup. It was never clear to me why we added CPATH and LIBRARY_PATH to MacPorts base, since the existing CPPFLAGS and LDFLAGS we set in the configure phase should have the same effect for properly-behaved ports, and improperly-behaved ports should be fixed. Now that Xcode 4.2 users are using clang, and clang does not use CPATH or LIBRARY_PATH [1], it may truly be time to admit that CPATH and LIBRARY_PATH are not helping us (they are merely causing those of us who don't use clang to commit ports that may not work for users using clang), and remove them. Then again, this may be fixed in future versions of clang. CPATH support was already added [2]; adding LIBRARY_PATH support [3] has not been discussed yet however. Out of curiosity, why are you needing to remove CPATH? What problem is having it set causing you? [1] http://lists.macosforge.org/pipermail/macports-dev/2011-August/015543.html [2] http://llvm.org/bugs/show_bug.cgi?id=8971 [3] http://llvm.org/bugs/show_bug.cgi?id=10296 _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
