[MacPorts] #51726: Gildas Install Fail
MacPorts
noreply at macports.org
Thu Feb 6 05:46:01 UTC 2020
#51726: Gildas Install Fail
------------------------+----------------------
Reporter: jtb1435@… | Owner: bardeau
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords:
Port: gildas |
------------------------+----------------------
Comment (by ryandesign):
This is basically the same as #59753 now.
Back when this ticket was filed, MacPorts used the same default C++ stdlib
as Apple, which meant that on 10.8 and earlier we used libstdc++. But
gildas has its build system hardcoded to use `-lc++` when linking
something that was built with clang++, which would have been the wrong
decision on 10.8 and earlier back then. clang++ would have built stuff
using libstdc++, and then when it came time to link, gildas would try to
link that with libc++, which couldn't possibly work.
But now MacPorts 2.6.0 has been released, in which we changed the default
C++ stdlib for 10.6-10.8 from libstdc++ to libc++ for better compatibility
with newer software requiring C++11 and later. This should mask the
`-lc++` problem in the gildas build system, except that (per #59753) the
portfile isn't passing the necessary `-stdlib=...` flag when building
things with clang++, so it's still (erroneously now) building things for
the compiler's default of libstdc++.
This problem would not occur on 10.9 or later, where Apple's default C++
stdlib is libc++, which explains why the user no longer sees the problem
after upgrading the OS.
--
Ticket URL: <https://trac.macports.org/ticket/51726#comment:24>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list