#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@…): If a compiler even knows about -std=c++11 it will be the same as -std=c++0x for it as far as I know, c++0x was just the name before they knew what year it would finally be ratified and when they came up with the final name 0x became an alias for it. http://clang.llvm.org/cxx_status.html lists what version of clang various c++0x/c++11 features were first added, I wouldn't be surprised if XCode's clang/libc++ is too old to support everything mkvtoolnix uses, but I'd think the latest clang and latest libc++ out of ports would since Clang has full C++11 support now. But since boost was compiled with the defaults (clang 3.2 and gcc4.2-like libstdc++) I think there's still going to be trouble using it when compiling the app with clang 3.4 libc++. See e.g. #38374. Boost itself was also compiles without -std=c++11, I don't know if this makes as big a difference as the older compiler and much older stdlib features. I really think embedded static boost builds like suggested in the ticket you abandoned for this one (#34806) may be the best way to handle this. Boost is big and complex and really wants to be used with the exact same stdlib/language features as it was compiled with in my experience, and there's no one-size-fits-all boost for MacPorts that can do that. -- Ticket URL: <https://trac.macports.org/ticket/40231#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X