Bug 2187970
Summary: | Julia fails to start: libopenblas64_.so library can’t be found | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kennedy Caisley <kcaisley> |
Component: | julia | Assignee: | Milan Bouchet-Valat <nalimilan> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 38 | CC: | chris, mtasaka, nalimilan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | https://discussion.fedoraproject.org/t/julia-installing-improperly-fedora-38/81080 | ||
Whiteboard: | |||
Fixed In Version: | julia-1.9.0-2.rc2.fc38 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-04-28 02:36:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kennedy Caisley
2023-04-19 09:55:38 UTC
Good catch. This is because OpenBLAS is no longer detected automatically as a dependency. You can install manually openblas-threads64_ if you don't want to wait for the fix. (In reply to Milan Bouchet-Valat from comment #1) > Good catch. This is because OpenBLAS is no longer detected automatically as > a dependency. You can install manually openblas-threads64_ if you don't want > to wait for the fix. Thank you for looking into this, I really appreciate your help. I'm curious what the '_' suffix on the package name signifies; the description indicates it is a 'symbol name suffix'? Your suggested temporary fix works for me. Julia starts and one can import standard libraries and plot functions, etc. When loading the Julia REPL, however, I did notice a non-blocking error: ┌ Error: Error during initialization of module CHOLMOD │ exception = │ could not load library "libcholmod" │ libcholmod.so: cannot open shared object file: No such file or directory └ @ SparseArrays.CHOLMOD /usr/share/julia/stdlib/v1.9/SparseArrays/src/solvers/cholmod.jl:242 Could this potentially indicate another dependency that should be marked for install alongside the main Julia package? FEDORA-2023-17a5e4ca79 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-17a5e4ca79 (In reply to Kennedy Caisley from comment #2) > (In reply to Milan Bouchet-Valat from comment #1) > > Good catch. This is because OpenBLAS is no longer detected automatically as > > a dependency. You can install manually openblas-threads64_ if you don't want > > to wait for the fix. > > Thank you for looking into this, I really appreciate your help. I'm curious > what the '_' suffix on the package name signifies; the description indicates > it is a 'symbol name suffix'? Yes, Julia uses an OpenBLAS with symbol names suffixed with _64 to avoid conflicts if one links to a library which uses a standard (LP64 rather than ILP64) OpenBLAS. > Your suggested temporary fix works for me. Julia starts and one can import > standard libraries and plot functions, etc. > > When loading the Julia REPL, however, I did notice a non-blocking error: > > ┌ Error: Error during initialization of module CHOLMOD > │ exception = > │ could not load library "libcholmod" > │ libcholmod.so: cannot open shared object file: No such file or directory > └ @ SparseArrays.CHOLMOD > /usr/share/julia/stdlib/v1.9/SparseArrays/src/solvers/cholmod.jl:242 > > Could this potentially indicate another dependency that should be marked for > install alongside the main Julia package? Damn. Of course the same change needs to be applied to SuiteSparse. I'll push a fix. It's really unfortunate that tests are run during the build rather than after installing the package on a clean system. FEDORA-2023-17a5e4ca79 has been pushed to the Fedora 38 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-17a5e4ca79` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-17a5e4ca79 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-b17d483574 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b17d483574 FEDORA-2023-b17d483574 has been pushed to the Fedora 38 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-b17d483574` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b17d483574 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-99fd4698da has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-99fd4698da FEDORA-2023-99fd4698da has been pushed to the Fedora 38 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-99fd4698da` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-99fd4698da See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-99fd4698da has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |