* On 2023-07-11 at 13:40 BST, Greg Troxel wrote:
This is a very minor change from longstanding practice: adding a GCC_REQD automatically based on USE_LANGUAGES. My impression is that ~everyone thinks this is a good change but there just have been enough round tuits. My impression is that ~everyone thinks that setting GCC_REQD based on language version is at least partially kludgy.
I'm pretty sure I've said this before, but just in case I haven't done so explicitly, and in case anyone cares in terms of votes for the direction to take or whatever, and to be completely clear that I am not part of "~everyone":
I think the whole GCC_REQD thing is stupid and should be ripped out completely.
The only sensible way for someone to build a set of software from pkgsrc is to calculate beforehand what GCC they need that is able to build all of it, and use that for everything. I've done this for over 10 years, have put a lot of effort into ensuring it works great, and have posted multiple times over the years on how this all works, along with implementing the *_GCC_RUNTIME stuff so that you do not end up with DEPENDS on an entire compiler package.
Building N versions of lang/gcc at different times depending on which order you build packages in and which GCC_REQD you encounter, and ending up with multiple libstdc++'s and runtime dependencies on full compiler packages, is clearly ridiculous.
-- Jonathan Perkin - mnx.io - pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com