On Tue, 8 Mar 2022, Axel Braun wrote:
Hello Dieter,
Am Dienstag, 8. März 2022, 17:44:13 CET schrieb dieter:
adding the compiler option fixed the problem for Leap 15.4. Other builds are running to make sure it does not break the rest.
Thanks for the hint!
Thanks for the confirmation that this was indeed the problem.
With the additional information from Pedja that libpoppler for Leap 15.4 is already being built using GCC-11 and from Richard better not to mix C++17 binaries generated by GCC-7 and GCC-11 the better solution is to build also gdcm for Leap 15.4 using GCC-11.
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? (Not to mention the exta spins one needs to take with regard to the python 3.6 stack. Different area, similar issue)
Mixing compiler-versions is OK as long as you are not ending up with experimental ABIs. I was pointing out that GCC-7 still has an experimental C++17 ABI (on the library side), that can, but needs not to, result in issues. So yes, I would also suggest to build gdcm with GCC-11 (but I'd also argue that building poppler with the non-system compiler was a bad idea). Richard. -- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Ivo Totev; HRB 36809 (AG Nuernberg)