llvm12 installs a config snippet to /etc/ld.so.conf.d/ to add the compat libraries for llvm 12 into the search path. Packages that do this still need to explicitly call ldconfig in their RPM scriptlets, because file triggers do only activate for installing things into %{_libdir} directly. The "%ldconfig_scriptlets" macro does not help in this case, because it expands to an empty string on all current Fedora releases, so this probably needs to be handled "manually" / the old way with an explicit %pre/post/trans/un scriptlet. This issue manifests only in some cases (I think probably depending on the exact installation order in an RPM transaction), but if it happens, this missing ldconfig call results in programs not being able to find llvm 12 libraries, for example, rustc sometimes fails with this error: error: process didn't exit successfully: `/usr/bin/rustc -vV` (exit status: 127) --- stderr /usr/bin/rustc: error while loading shared libraries: libLLVM-12.so: cannot open shared object file: No such file or directory Running "ldconfig" manually in the mock chroot makes this error go away, until the mock chroot is cleaned and reinstalled, and then it happens again. (I'm not sure why this is the case, but this error only happens in mock builds that use QEMU-emulated s390x chroots, both locally, and in COPR, but not consistently. koji does not seem to be affected at all, so maybe this is impacted by a race condition, as well.)
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This issue is still present in rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
If rust is still affected by this, perhaps this should be moved to the llvm package instead?
Moving this to llvm since that is what rust is actually using (linked against)
Right - as far as I can tell, it affects *all* versions of llvm, including the compat packages. This used to be a problem with llvm12 when Rust used llvm12, but it is not specific to Rust. The fact that installing LLVM doesn't cause problems in most cases seems to be pure luck, as the RPM ldconfig trigger seems to trigger for unrelated reasons, even if installing llvm doesn't do it when it should.
I proposed a fix at https://src.fedoraproject.org/rpms/llvm/pull-request/192 This will have to be backported to compat packages later.
FEDORA-2024-a075b55246 (llvm17-17.0.6-7.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-a075b55246
FEDORA-2024-a075b55246 (llvm17-17.0.6-7.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-b536b520c2 (llvm16-16.0.6-8.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-b536b520c2
FEDORA-2024-2b1a16c9ea (llvm15-15.0.7-8.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-2b1a16c9ea
FEDORA-2024-b536b520c2 (llvm16-16.0.6-8.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-2b1a16c9ea (llvm15-15.0.7-8.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.