meson-python: Builds incomplete wheel for SciPy because "File could not be mapped to an equivalent wheel directory"
This is on gentoo with gentoo’s python3.9. @rgommers
https://github.com/mkoeppe/sage/runs/7659423834?check_suite_focus=true
e75b6879f2d8 /sage # cat logs/pkgs/scipy-1.9.0rc3.log
[...]
+ meson install --destdir /sage/local/var/lib/sage/venv-python3.9/var/tmp/sage/build/scipy-1.9.0rc3/src/.mesonpy-cjaz4nzj/install
WARNING Using heuristics to map files to wheel, this may result in incorrect locations
WARNING File could not be mapped to an equivalent wheel directory: /sage/local/var/lib/sage/venv-python3.9/var/tmp/sage/build/scipy-1.9.0rc3/src/.mesonpy-cjaz4nzj/install/usr/lib/python-exec/python3.9/../../../lib/python3.9/site-packages/scipy/__config__.py (/usr/lib/python-exec/python3.9/../../../lib/python3.9/site-packages//scipy/__config__.py)
WARNING File could not be mapped to an equivalent wheel directory: /sage/local/var/lib/sage/venv-python3.9/var/tmp/sage/build/scipy-1.9.0rc3/src/.mesonpy-cjaz4nzj/install/usr/lib/python-exec/python3.9/../../../lib/python3.9/site-packages/scipy/version.py (/usr/lib/python-exec/python3.9/../../../lib/python3.9/site-packages//scipy/version.py)
WARNING File could not be mapped to an equivalent wheel directory: /sage/local/var/lib/sage/venv-python3.9/var/tmp/sage/build/scipy-1.9.0rc3/src/.mesonpy-cjaz4nzj/install/usr/lib/python-exec/python3.9/../../../lib/python3.9/site-packages/scipy/_lib/_ccallback_c.cpython-39-x86_64-linux-gnu.so ({moduledir_shared}/_ccallback_c.cpython-39-x86_64-linux-gnu.so)
WARNING File could not be mapped to an equivalent wheel directory: /sage/local/var/lib/sage/venv-python3.9/var/tmp/sage/build/scipy-1.9.0rc3/src/.mesonpy-cjaz4nzj/install/usr/lib/python-exec/python3.9/../../../lib/python3.9/site-packages/scipy/_lib/_test_ccallback.cpython-39-x86_64-linux-gnu.so ({moduledir_shared}/_test_ccallback.cpython-39-x86_64-linux-gnu.so)
[...]
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 31 (30 by maintainers)
It’s in the one we are cooking right now.
A bunch more fixes were merged, including for absolute paths in
intro-install_plan.json
with Meson 0.63.2. With the main/master version ofmeson
,meson-python
andscipy
I’m ~99.x% sure this is fixed. WIth current released versions it probably isn’t. We should get ameson-python
release very soon (all pending PRs were merged), and ascipy
1.9.2 release with backports of the relevant build fixes within 1-2 weeks.Thanks. I’m afraid I can’t offer much help right now but if you need me to quickly check something or run some mechanical task, I can do that.
That was released over the weekend without it (actually, the branch was cut before this discussion, I tried to mark it for backporting late Friday, but the release manager didn’t notice and regenerate the release once the CI was fixed Saturday morning).
We’ll see if it gets into a .3 release though.