> On 2 Sep 2016, at 7:41 pm, René J.V. Bertin <[email protected]> wrote: > > 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 …
you are behind the times. gcc 6.2 is the current pro version… > >> 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). Fixing that is I think part of the update. Not being able to build clang with gcc > 4 was a major issue as it meant we could not have a stack of my experimental software built with gcc > 4, as ROOT internally builds LLVM (which actually is where the issue is) as part of the cling interpreter. Chris
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
