[MacPorts] #54766: Does port:clang*'s libstdcxx have to be default?
MacPorts
noreply at macports.org
Thu Sep 7 08:52:38 UTC 2017
#54766: Does port:clang*'s libstdcxx have to be default?
----------------------------------+---------------------------------
Reporter: RJVB | Owner: MarcusCalhoun-Lopez
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: clang-4.0 clang-5.0 |
----------------------------------+---------------------------------
Comment (by MarcusCalhoun-Lopez):
I am fine not forcing the installation of GCC with Clang unless absolutely
necessary.[[BR]]
There are a few things, however, that I need to look into before making
the change.
1. If GCC is **not** installed, does {{{-stdlib=macports-libstdc++}}}
cause a compile-time error or silently do the wrong thing?
1. To avoid multiple recompilations of clang, can {{{-stdlib=macports-
libstdc++}}} now use gcc7 header files?
1. To avoid multiple recompilations of clang, add
[https://github.com/macports/macports-
ports/commit/be6401d19706f7317979dfbd680592cee5f7cf9d xcrun].
It might be a few days before I can look into these.
--
Ticket URL: <https://trac.macports.org/ticket/54766#comment:18>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list