[MacPorts] #44722: fswatch @1.4.0 update
MacPorts
noreply at macports.org
Thu Aug 21 05:27:54 PDT 2014
#44722: fswatch @1.4.0 update
------------------------------------+---------------------------------
Reporter: enrico.m.crisostomo@… | Owner: macports-tickets@…
Type: update | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.3.1
Resolution: fixed | Keywords: maintainer haspatch
Port: fswatch |
------------------------------------+---------------------------------
Comment (by enrico.m.crisostomo@…):
Replying to [comment:5 cal@…]:
> Yeah, unfortunately if you want full C++11 support you're limited to
Mavericks and beyond.
>
> The rationale behind that is that only libc++, Apple's new C++ runtime
library, supports C++11 while the previous libstdc++ from GCC is stuck at
the equivalent of what it was in GCC 4.2 due to licensing reasons.
>
> However, the default C++ runtime didn't change until Mavericks, which
means on 10.8 and below (where libstdc++ is being used) the compiler
understands C++11 (because you can switch to libc++ manually) but the
runtime does not. Switching to libc++ for this port is not an option
either, because both runtimes are incompatible and cannot be mixed in the
same binary, i.e., you could no longer link against your library and a
different C++ library in MacPorts. Consequently, the choice of C++ runtime
library cannot be made locally for a single port, but must be done at a
global level in all of MacPorts at once, and we're not confident enough
and lack the manpower to ignore Apple's default and go with libc++ on 10.7
and beyond.
Thank you very much for the explanation, now that's clear.
I've just submitted (yet) another patch for 1.4.1: I added an Autoconf
check for <mutex> and <atomic> and disabled that functionality on systems
missing the new runtime.
--
Ticket URL: <https://trac.macports.org/ticket/44722#comment:6>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list