[MacPorts] #49709: cmake, gnuradio, gr-foo, gr-ieee802-11, gr-ieee802-15-4, volk: just use cxx11 1.0 portgroup
MacPorts
noreply at macports.org
Wed Nov 18 06:55:47 PST 2015
#49709: cmake, gnuradio, gr-foo, gr-ieee802-11, gr-ieee802-15-4, volk: just use
cxx11 1.0 portgroup
-------------------------------------------------+-------------------------
Reporter: ryandesign@… | Owner: michaelld@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords: haspatch
Port: cmake gnuradio gr-foo gr- |
ieee802-11 gr-ieee802-15-4 volk |
-------------------------------------------------+-------------------------
Comment (by michaelld@…):
The cxx11 1.0 port group only handles C++11 for libc++. It does not handle
C++11 for libstdc++. From the comment in that PortGroup:
{{{
# Compilers supporting C++11 are GCC >= 4.6 and clang >= 3.3.
# As we only support libc++, clang is implicitly required.
# Blacklist all GCC compilers to not accidentally pull in libstdc++.
# We do not know what "cc" is, so blacklist it as well.
}}}
There have been past discussions on the MP-dev list about this topic, and
the conclusion is that there is no generic way to handle libstdc++ and
C++11 within the current MP framework. That said, my way here works for
the GR ports & is used by some users / customers (per email feedback).
Until MP comes up with a good way of handling libstdc++ and C++11, I'm
going to leave these in place; maybe update them to use gcc5.
There is a lot of redundancy in the GR-related ports, quite true. I will
look into creating a GR PortGroup file sooner or later, which incorporates
the common parts of the GR Portfiles as well as some optional function to
handle C++11 (such that there's just 1 place to make any C++11 changes,
assuming MP ever gets to that point).
--
Ticket URL: <https://trac.macports.org/ticket/49709#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list