[MacPorts] #40231: mkvtoolnix: fix build with clang

[MacPorts]

#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 ryandesign@…):

 Replying to [comment:4 ecronin@…]:
 > http://clang.llvm.org/cxx_status.html lists what version of clang
 various c++0x/c++11 features were first added,

 Yes, that was brought to my attention on the mailing list, which prompted
 my further investigation, which led to this ticket.

 > 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.

 See my patch. I tested all clangs I could and listed in compiler.blacklist
 those that don't pass the configure script check. The remaining ones,
 including the very latest pre-release of clang 3.4, fail to build the
 port, as I described at the top of this ticket.

 I did not test the libcxx port. It does not appear to be particularly
 recent.

 > 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 have no idea how this stuff works or if that matters.

 > 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.

 If you think that's the answer, re-open #34806 and come to an agreement
 with Jeremy H.S., who said there that that won't work but didn't
 elaborate.

-- 
Ticket URL: <https://trac.macports.org/ticket/40231#comment:5>
MacPorts <http://www.macports.org/>
Ports system for OS X