On Fri, 08 Jan 2021, 09:55:02 +0100, Richard Biener wrote:
On Fri, 8 Jan 2021, Aaron Puchert wrote:
Am 07.01.21 um 17:37 schrieb Manfred Hollstein:
Hi there,
I am trying to build all packages I'm somehow involved with for Leap 15.3, but fail with "rust". rust-1.47 require llvm-devel >= 8.0 (9.0 since rust-1.48), but this cannot be found for Leap 15.3. As Leap 15.2 comes with llvm-devel-9.0.1 and since Leap 15.3 should provide everything Leap 15.2 has (at least that's my understanding), why is it missing? Can I do anything about this? If so, what?
I think that's a fallout of the "Closing the Leap gap" effort and the divergence of Leap and SLE in the LLVM area. SUSE decided to update the "llvm" metapackage from 5 to 7 for SLE 15 SP1, but didn't update for SP2, while in Leap 15.2 we went to 9. It's likely going to stay that way, although I can't say anything about the technical details here [1]:
One possibility is to not require llvm-devel >= $ver but a specific one (usually the >= will break anyway at some point). For Leap 15.3 llvm9-devel should work as well as llvm11-devel. Note you're not going to have the 'llvm-devel' style symlinks but have to use version specific tool names (whatever they are). Mesa is using llvm11 via such mechanism for 15.3.
Thanks for your hints, Aaron and Richard! I'll see if I can convince the rust package maintainers to accept such a change ;) Will try if it works in all situations.
That's how packages like firefox use newer GCC as well, require say gcc10-c++ and build with CXX=g++-10 (or set up your own directory with symlinks for insane build systems and adjust your PATH to prefer that).
Yep, well known example. Cheers. l8er manfred
For Leap 15.3 we will have differing 'llvm' packages I'm sure (not defaulting to llvm7 but llvm11).
Perhaps the solution here is that we inherit the llvm{7,9,11} packages from SLE but not the llvm metapackage. Not sure if that's possible. Perhaps we should also not inherit llvm5, since I removed that from Leap 15.2 already [2] and there is no reason to reintroduce it in my view.
I have no hopes for a simple solution ;) Note for SLE you can't remove packages :/ But since Leap 15.3 is at least an alternate media we can possibly block them to not appear there.
Richard.
Otherwise Leap 15.3 should have not only llvm9 [3] inherited from SUSE:SLE-15-SP2:Update, but also llvm11 [4] inherited from SLE-15-SP3:GA, SUSE:although I can't find binary packages for the latter in [5].
Best regards, Aaron
[1] https://bugzilla.opensuse.org/show_bug.cgi?id=1179155#c12 [2] https://build.opensuse.org/request/show/776163 [3] https://build.opensuse.org/package/show/openSUSE:Leap:15.3/llvm9 [4] https://build.opensuse.org/package/show/openSUSE:Leap:15.3/llvm11 [5] https://download.opensuse.org/distribution/leap/15.3/repo/oss/x86_64/