[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     |
---------------------------+----------------------

Comment (by jeremyhu):

 If you get 'C compiler does work: no' from configure, that means that
 you've misconfigured your compiler setting somehow.  That has nothing to
 do with individual ports.  Every port will fail with that issue until you
 resolve your configuration problem.

 Usually a quick look in config.log will immediately reveal what the
 problem is.

 Yes, as I noted, clang does not officially support darwin-ppc.  I think
 there are literally two people (myself included) who have worked on trying
 to bring clang support to Lion and earlier (including to ppc) over the
 past 5 years, and neither of us has really put in any effort since around
 llvm-3.8.  Ken has done a great job of trying to revive that effort, but
 there is a lot of entropy to fight, and bootstrapping the build process is
 even harder than ever.  I don't see a way of doing the bootstrap without
 using a second system to cross compile (or using prebuilt binaries).

 If I was going to live on darwin-ppc right now, I'd definitely be using
 FSF gcc.  If it was a hobby system (as I suspect it is for just about
 anyone still using it), I'd resurrect the ppc work.

 clang++-mp-3.4 is not "only a wrapper around g++".  It's quite a stable
 and usable compiler that supports a wide array of platforms.  However, the
 ancient platform that you are running on is simply not one of them, so it
 calls out to g++ for darwin-ppc.  In 3.4, that is only for ppc.  In very
 earlier versions of clang that did not support C++, that was also done for
 C++ on Intel.

 MacPorts does not actually support the use of GCC as a primary toolchain,
 and we don't support ppc any more.  If you really want to use darwin-ppc
 (which was EOLd over a decade ago), you're going to hit many road bumps
 and will need to submit patches to address the failures you run into.  You
 will also need to manage your compiler settings manually.  Most MacPorts
 developers do not even have systems with which to reproduce the issues you
 are reporting or to test the relevant changes.

 ---

 I believe you will need to build libunwind for intel-only in order to
 build libcxx universal in order to build clang-3.7 in order to build cmake
 in order to build clang-5.0 ...  but Ken can point you to more specific
 steps.

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