[MacPorts] #55592: libunwind @5.0.1: unrecognized command line option '-stdlib=libstdc++' with clang-3.4

[MacPorts]

#55592: libunwind @5.0.1: unrecognized command line option '-stdlib=libstdc++' with
clang-3.4
---------------------------+----------------------
  Reporter:  sideeffect42  |      Owner:  jeremyhu
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.4.2
Resolution:  wontfix       |   Keywords:
      Port:  libunwind     |
---------------------------+----------------------
Changes (by jeremyhu):

 * status:  assigned => closed
 * resolution:   => wontfix


Comment:

 > So many ports that just don't compile properly with clang.

 Which ones?  pretty much all ports build just fine with clang.  I spent
 quite a bit of time ~3-5 years ago making sure all of our ports were
 building fine with clang.  There are a few buggy ports that I haven't had
 resources to fix that clang properly errs out on rather than violating
 language specifications and producing an executable with undefined
 behavior.  There are also a couple very fringe cases where GCC extensions
 are used by projects that clang doesn't support, but that's again a
 project issue and a very rare one.

 clang has been the defacto compiler on darwin for almost a decade now, on
 FreeBSD for I believe 5+ years.

 @ryandesign: clang++-mp-3.4 understands -stdlib=libstdc++.  clang-3.4
 execs g++ for -arch ppc and lipos the result back into the output file.
 g++ doesn't understand -stdlib=libstdc++, so that's why the message is
 about g++.

--
Ticket URL: <https://trac.macports.org/ticket/55592#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS