Am Freitag, 11. März 2022, 09:37:01 CET schrieb Richard Biener:
On Thu, 10 Mar 2022, Axel Braun wrote:
Hello richard,
Am Mittwoch, 9. März 2022, 13:38:36 CET schrieb Richard Biener:
...
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).
So, proposal is to follow the path which you do not in general propose, just because one made a wrong turn.
I tested a bit using the gcc11-c++ compiler, which alone does not give a working compilation (bunch of error messages). i gave up at some point
For now https://build.opensuse.org/request/show/960283 is waiting for approval (ideally after review from a graphics maintainer)
The
BuildRequires: gcc-c++ >= 11
is going to fail on Leap, you'd have to use
BuildRequires: gcc11-c++
and in %build do
CXX=g++-11
and hope that cmake picks that up ...
Thank you for the hint. With some conditions in the spec file it now builds for Leap, and fails for TW. I guess this is due a recent poppler-update (again): https://paste.opensuse.org/96354932 My guess is that is for upstream to fix Cheers Axel