So you are proposing to set a BuildRequirement to gcc11-c++ ? unfortunately its not just that easy. And in general - should mixing compiler versions not be forbidden if this creates issues? The problem with mixing code generated by different compiler versions arises if a specific ABI changes between these two versions. In this case - according to Richards mail - when using gcc-7 with the switch "-std=c++17" the generated code should not be mixed with gcc-11 generated code for C++17. So if the libpoppler version in Leap 15.4 using C++17 features is already built with GCC-11 and exports interfaces requiring its users also to be built with C++17 support then these users ideally should also be built using GCC-11. Whereas dependencies further down the line which do not require to be built with C++17 support can be built using GCC-7, e.g. if libgdcm fully encapsulates the interface to
Hi Axel, On Tue, 08 Mar 2022 20:18:38 +0100 Axel Braun wrote: libpoppler and users of libgdcm do not need C++17 support they can be built using GCC-7. I am afraid I can not tell how risky the mixing is and how obvious problems would be. Kind regards, Dieter