Consequences of using MacPorts GCC as a fallback compiler on PowerPC
Kenneth F. Cunningham
ken.cunningham.webuse at gmail.com
Fri Mar 23 01:23:23 UTC 2018
On 2018-03-22, at 5:11 PM, Ryan Schmidt wrote:
> There are already ports out there, and installed on user systems, and binaries being distributed that were built by our buildbot, that were built with a MacPorts gcc without -D_GLIBCXX_USE_CXX11_ABI=0 set. These would be ports that do not use the cxx11 1.1 portgroup and that don't use C++11.
I can't help but think that any ports where the change in LIBCXX ABI was an issue have been identified as build failures on the buildbots < 10.9, and the cxx11 1.1 PG was added.
Any of the very few others I might have upgraded separately to build with gcc6 on PPC for C11 or other reasons, aren't using the changed c++11 features of libstdc++ anyway, or they would be in the cxx11 1.1 PG.
So - do they all really need to be rebuilt? I'm trying to think if there are any cases of incompatibility that might slip through this logic, and none are coming to mind just now….
Ken
More information about the macports-dev
mailing list