#40231: mkvtoolnix: fix build with clang ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: mkvtoolnix | ---------------------------+-------------------------------- Comment (by ecronin@…): Replying to [comment:7 jeremyhu@…]:
The other alternative is to have a C++ Flag Day where we simultaneously revbump every C++ project that uses C++ across an API boundary to start using libc++ instead of libstdc++.
Continuing to use a gcc4.2 based libstdc++ (and ancient gcc's on pre- XCode4 OSs) is going to be a bigger and bigger issue for C++ code I think. Switching to always using clang/libc++ as the default compiler is probably worth exploring (I don't know if current xcode-dependent default C compiler and clang++ or clang/clang++ is better). Boost is probably going to keep dropping support for those old versions, meaning no port that depends on it will work on those older OSs due to C++ runtime mixing (I didn't follow the thread on the most recent update closely, but it looks from the Portfile blacklist like boost might now be using a newer FSF gcc on some older OS X releases? that can't be good...). Boost is also particularly problematic as it is so tightly entangled with the particular compiler version and options used to compile it. I think the stdlib is the biggest issue, but I don't know for sure what gets built differently in the boost libraries when you compile with --std=c++11, and how that interacts with the template portions of boost that are compiled later in some program without using c++11... -- Ticket URL: <https://trac.macports.org/ticket/40231#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X