expected LLVM 16.x but found 17.0.3 using /usr/bin/llvm-config-16 Reproducible: Always Steps to Reproduce: 1. /usr/bin/llvm-config-16 --version 2. 3. Actual Results: 17.0.3 Expected Results: 16.x
I can't reproduce this issue. $ rpm -q llvm16-devel llvm16-devel-16.0.6-5.fc39.x86_64 $ /usr/bin/llvm-config-16 --version 16.0.6 $ alternatives --list | grep llvm-config llvm-config-16 auto /usr/lib64/llvm16/bin/llvm-config-16-64 llvm-config auto /usr/bin/llvm-config-64 llvm-config-17 auto /usr/bin/llvm-config-64 @skrochen , could you provide the same output of your system, please?
Sorry, I did the following: before I saw your question. sudo ln -sf /usr/lib64/llvm16/bin/llvm-config /etc/alternatives/llvm-config-16 [pappy@dave-the-dog ~]$ rpm -q llvm16-devel llvm16-devel-16.0.6-5.fc39.x86_64 [pappy@dave-the-dog ~]$ /usr/bin/llvm-config-16 --version 16.0.6 [pappy@dave-the-dog ~]$ alternatives --list | grep llvm-config failed to read link /usr/lib64/libOpenCL.so: No such file or directory ... not so sure what's going on here
I can remove and reinstall llvm16 if required
[pappy@dave-the-dog ~]$ alternatives --list | grep llvm-config llvm-config-17 auto /usr/bin/llvm-config-64 llvm-config auto /usr/bin/llvm-config-64 llvm-config-16 manual /usr/lib64/llvm16/bin/llvm-config
I managed to reproduce it. Before the upgrade: $ update-alternatives --list | grep llvm-config llvm-config auto /usr/bin/llvm-config-64 llvm-config-16 auto /usr/bin/llvm-config-64 After the upgrade: $ update-alternatives --list | grep llvm-config llvm-config-16 auto /usr/bin/llvm-config-64 <= This is wrong. llvm-config auto /usr/bin/llvm-config-64 llvm-config-17 auto /usr/bin/llvm-config-64 $ update-alternatives --display llvm-config-16 llvm-config-16 - status is auto. link currently points to /usr/bin/llvm-config-64 /usr/bin/llvm-config-64 - priority 64 /usr/lib64/llvm16/bin/llvm-config-16-64 - priority 64 Current `best' version is /usr/bin/llvm-config-64. The %postun is not behaving well.
"llvm-config-16 auto /usr/bin/llvm-config-64 <= This is wrong." <== Yes, this is where the symlink pointed to for me as well before I edited it ...
I proposed a fix at https://src.fedoraproject.org/rpms/llvm/pull-request/188
The fix is now available in Rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2023-300c4820ee Let's test it there first before we integrate it into a stable release.
FEDORA-2023-3bd19e87a3 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3bd19e87a3
FEDORA-2023-3bd19e87a3 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3bd19e87a3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3bd19e87a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-3bd19e87a3 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.