On Friday September 02 2016 13:45:56 Lawrence Velázquez wrote: >> Or is it something that will in fact mostly/only benefit Linux users? > >Yes. This is meant to keep Clang compatible with ABI changes to GCC 5.1's >libstdc++.
That's about time ... GCC 6.1 is out ... >P.S. Incidentally, this implies that g++ 4.x is also ABI-incompatible with >libstdc++ 5.1. Have we encountered any issues along these lines? Funny enough I haven't noticed any issues with that on Linux; at some point I started using GCC 5 (and now GCC 6) without rebuilding my whole system, and haven't run into any issues. Maybe that means that libstdc++ is linked in as a private library and designed in such a way that different versions can be loaded in memory? I do remember that clang itself cannot be built with GCC 5 (on Linux, clang 3.5 IIRC). R _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
