On Mar 16, 2014, at 19:49, Brandon Allbery wrote: > http://trac.macports.org/wiki/FAQ#libcpp > > Linux gets around this by forcing everything to the new runtime; Apple will > not ship GPL3 stuff so stuck to older gcc with the older runtime, until they > moved to clang completely in 10.9 and switched to clang's C++11 runtime. > (gcc/g++'s C++11 runtime is GPL3+ only.)
But how can the situation be any different if system libraries use either the GNU C++11 runtime or the clang one? > > Hi, "C++11" refers to a standard defined by a standards committee. The > problem is a *licensing* issue, and Apple made its choice in that matter and > nobody can do anything about it. Sigh ... something like "or how lawyers can mess up perfectly good standards"? Or does the standard not cover the ABI? R. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
