[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 ecronin@…):

 Replying to [comment:14 jeremyhu@…]:
 > Replying to [comment:12 ecronin@…]:
 >
 > > except maybe ditching the system compilers completely and using a
 newer FSF g++ for all of macports.
 >
 > NO!  That will not be done.  We will not be going to FSF for compilers.
 The goal is to use the host C++ runtime, not a conflicting one.
 >

 I only meant on PPC where clang isn't viable.  There's no good option
 there, but most macports software probably doesn't touch C++ system-
 provided libraries, so as long as everything in macports uses new
 libstdc++ and gcc it should be internally consistent.  Software that
 depends on OS X frameworks and would have conflicting runtimes probably
 doesn't work on something that old to begin with, but more general cross-
 platform software could probably still work with newer compilers than
 gcc4.0 and gcc4.2.  I know you'd like to axe everything older than Lion
 but there are still a lot of people with PPCs out there and macports is
 one of the few options for them.  I don't know if there's anybody
 unofficially maintaining the older PPC OSs in base, this would be
 something for them to look into not you...

 > > This was just an excuse to play around with the latest clang a bit,
 I'm throwing in the towel on any further attempts.  Switching to libc++ is
 probably worth sending over to the -dev list for discussion for people
 more knowledgeable than me on OS X C++ development.  Won't that have the
 same incompatible mangling/runtime problems with linking in any required
 system frameworks on pre-Mavericks OSs we're having here, though?
 >
 > If *everything* is using libc++, we will have issues when using the host
 C++ frameworks that are using libstdc++, but I don't think any of our
 ports actually do that.

 Accelerate.framework is linked against libstdc++ on Lion at least, and I
 know there are ports that use it.

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