[macports-ports] branch master updated: cmake: require C++11 for both release and devel.

Ken Cunningham ken.cunningham.webuse at gmail.com
Tue Nov 7 03:34:23 UTC 2017

On 2017-11-06, at 7:13 PM, Ryan Schmidt wrote:

> Wow, this really sucks. It means that on Mountain Lion and earlier, cmake now depends on clang-5.0, clang-4.0, clang-3.9, clang-3.8, and clang-3.7, and on Lion and earlier, also clang-3.4. It also says all compilers are blacklisted so I'm not sure if it builds. Judging by the fact that binary packages were only produced for Mavericks and later, I'm guessing it does not build on earlier systems.

Yeah, Mike and I had a little chat about that a few weeks ago when this came through. This is presently a bootstrap issue for new installs on older systems. The c++11 requirement is right in the kitware commits, so that looks like a real deal. <https://gitlab.kitware.com/cmake/cmake/commit/c1f3eb9f2d628b2911aa17f65012fab0befc4b87>.

A cmake 3.8 port that doesn't require c++11 could be held back to bootstrap.

Or clang-3.7 (last one we have that builds with autotools) could be used to build cmake, I'm pretty sure that builds on everything 10.6 to 10.8.

Or even gcc6 could be used to build it (which is what we do on PPC).

But it has to be resolved.


More information about the macports-dev mailing list