In order to build LLVM 22, @tuliom would need the latest version of spirv-headers, included, as part of the Vulkan SDK side-tag, in this build: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0f635ac50e Tulio will request a freeze exception for LLVM 22, but he'll be blocked unless spirv-headers is available in Fedora 44. Therefore, I'd like to request a freeze exception for spirv-headers and the other packages that go with it. Reproducible: Always
Proposed as a Freeze Exception for 44-beta by Fedora user jexposit using the blocker tracking app because: In order to build LLVM 22, @tuliom would need the latest version of spirv-headers, included, as part of the Vulkan SDK side-tag, in this build: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0f635ac50e Tulio will request a freeze exception for LLVM 22, but he'll be blocked unless spirv-headers is available in Fedora 44. Therefore, I'd like to request a freeze exception for spirv-headers and the other packages that go with it.
I'm the person building LLVM 22 this time. I confirm that spirv-headers is a prerequirement for llvm22 via: spirv-headers <- spirv-llvm-translator <- libclc libclc is part of LLVM. I'd appreciate if this exception could be approved ASAP in order to create the LLVM22 side tag. Or please let me know if there are any other solutions that allow me to start building LLVM22 in a side tag before spirv-headers reaches stable.
Hey @tuliom > Or please let me know if there are any other solutions that allow me to start building LLVM22 in a side tag before spirv-headers reaches stable. You don't need to wait, you can tag it: $ koji tag <The side-tag you are using to build LLVM> spirv-headers-1.5.5-37.fc44 And, if this freeze exception is approved and spirv-headers is merged, you can untag it before you push your side-tag to Bodhi: $ koji untag <The side-tag you are using to build LLVM> spirv-headers-1.5.5-37.fc44 I hope this helps you continue with your work.
Why would we give LLVM 22 a freeze exception?
(In reply to Adam Williamson from comment #4) > Why would we give LLVM 22 a freeze exception? Adam, this is not a freeze exception for LLVM 22. It is a freeze exception for the Vulkan SDK. One of the packages of the Vulkan SDK is spirv-headers, which is a requirement for LLVM. With that said, the Fedora change for LLVM 22 gives an explanation: https://fedoraproject.org/wiki/Changes/LLVM-22 In summary: LLVM 22.1.0 got tagged 2 days ago. But we have been testing it on Copr since RC1 got released: https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm22/ I plan to ask a Beta freeze exception for LLVM 22 as soon as the side tag is ready, as proposed in the Fedora change.
> Adam, this is not a freeze exception for LLVM 22. I'm aware of that. But the only justification for *this* freeze exception is "we need it for LLVM 22". So there is only any point in giving this an FE if we are also inclined to give LLVM 22 an FE.
Discussed on the Fedora Blocker Review Meeting on March, 2nd 2026 with the resolution. Rejected Beta FreezeException We are not granting a Freeze Exception just for the purpose to support a potential future LLVM 22 Freeze Exception at this time, particularly since no coordinated request covering the full LLVM 22 stack has been formally presented for review and a candidate compose is already under testing. If LLVM 22 is proposed and accepted as a Freeze Exception later, the related dependencies can be considered together in a single, coherent request. See https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2026-03-02/f44-blocker-review.2026-03-02-17.00.log.txt