On 10-Oct-2015 22:50:12, David Sainty wrote:
just want to mention that this style of solution is probably wrong for C++. The problem with C++ is that, depending on package build ordering, packages may end up linking with multiple stdc++ libraries (and including different c++ includes) from different compilers.
The current GCC_REQD behaviour avoids this problem (at a hefty cost).
Interesting, because my test case for trying out changes is Taskwarrior which is C++. Although I don't think that last patch was "correct" I don't understand the problem with C++. Perhaps Taskwarrior isn't complicated enough for me to come across these issues? I thought by letting GCC_REQD do it's thing and only afterwards overriding it I'd be ok?