On Nov 6, 2017, at 21:40, Ryan Schmidt wrote: > On Nov 6, 2017, at 21:34, Ken Cunningham wrote: > >> 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. > > Yes I just saw your comments on GitHub: > > https://github.com/macports/macports-ports/commit/c8d94a92cb1d690a3dc052ff1ed7c0107af9b32a > > >> 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>. > > I know cmake master requires C++11. What I'm saying is that I don't think > 3.9.5 requires C++11. I'm checking on that now.
Yup, 3.9.5 builds fine with libstdc++. c8d94a92cb1d690a3dc052ff1ed7c0107af9b32a should be reverted.
