On Tue, Feb 07, 2017 at 10:02:57AM +0000, Stuart Henderson wrote:
> The simple fix for your issue would be to add a ${BASE_CXXLIB}, stdc++
> on base-is-gcc arches, c++ on base-is-clang ones, and replace all
> stdc++ in WANTLIB with that variable.
>
> But this is part of a wider problem that we don't have a good answer
> for.
>
> We have some libraries that are built with ports gcc or ports clang
> on some arch (-> estdc++).
>
All true, but here we can just figure out the library for the base
compiler and have a variable set according to that.
This would at least solve all the small ports "this uses the base C++
compiler".
For the rest, let's hope we can move to clang in the near future.
Another wacko possibility would be to enforce moving everything on the big
chains to a modern compiler... I believe the mixture of recent gcc and clang
to be more deadly than the mixture of old and new gcc. This is also an
issue with GL glue in xenocara...
the elephant being that libstdc++ and libestdc++ are about 99% ABI-compatible,
not 100%...
