JuliaPy / JuliaPy/PythonCall.jl
`libhdf5` not defined for `juliacall` `0.9.25` on M1 runner when using python built with openssl 1.x
- Dominant language
- Julia
- Stars
- 1.1k
- Forks
- 86
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 3
Description
**Affects:** JuliaCall
**Describe the bug**
Since `0.9.25` precompilation of HDF5 fails (only) on `macos-latest` M1 GitHub runner.
Here's an issue where we identified it:
https://github.com/JuliaIO/HDF5.jl/issues/1198
And here's a minimal repository reproducing it:
https://github.com/mtsokol/hdf5-bug
https://github.com/mtsokol/hdf5-bug/actions/runs/15098780219/job/42436980940
Pinning `juliacall` version to `0.9.24` fixes it:
https://github.com/mtsokol/hdf5-bug/pull/1
**Additional context**
Looking at the `0.9.25` diff my guess would be that it has something to do with OpenSLL_jll change.
Additionally, I reported 3 weeks ago: https://github.com/JuliaPackaging/Yggdrasil/issues/11077 which was HDF5 dependency juliapkg issue.
I had to pin `juliacall` only for `macos-latest`, as pinning it for all environments caused `ubuntu-latest` to fail with OpenSLL_jll dependency error.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the minimal repository and GitHub Actions run linked in the issue, then compare the juliacall 0.9.24 and 0.9.25 dependency changes, especially the OpenSSL_jll change. Reproduce HDF5 precompilation on the macOS M1 runner and Ubuntu, and consider the issue done when both environments work without platform-specific pinning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100