Handling C++11

Ken Cunningham ken.cunningham.webuse at gmail.com
Fri Jan 20 05:15:07 UTC 2017

It's growing on me.

This will be quite useful on 10.4 and 10.5 PPC, where it's the only
way forward, for gtk3 for example.

I noticed this method enables thread-local storage on 10.6, which
until now was not available (at least I didnt' figure it out).

There is a flag to compile libgcc so it defaults to the
gcc4-compatible ABI by default, for all those situations where the
CXX_FLAGS don't seem to be working right.

It looks like a nice option to have available for some situations,
therefore, even if the world of macports has moved on to libc++ and
that is the future.

Thanks for sorting it out.

On 1/19/17, Marcus Calhoun-Lopez <mcalhoun at macports.org> wrote:
>> On Jan 19, 2017, at 2:04 PM, Chris Jones <jonesc at hep.phy.cam.ac.uk>
>> wrote:
>> I don't think we should, under any circumstances, but making the use of
>> gcc to build c++ ports a standard practise.
> Just to be clear, the proposal is not to use gcc but to use clang with
> libstdc++ and *only* on systems where it has been requested.
> Your point, either way, remains valid.
> However, I would argue that the proposal is not about changing any existing
> practices.
> libc++ and clang would still, by far, be the best choices.
> LibcxxOnOlderSystems would still be the recommendation for older system.
> The proposal is only about attempting to respect what the user has
> requested.
> -Marcus

More information about the macports-dev mailing list