Search Criteria
Package Details: python-jaxlib 0.4.35-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-jaxlib.git (read-only, click to copy) |
---|---|
Package Base: | python-jaxlib |
Description: | XLA library for JAX |
Upstream URL: | https://github.com/jax-ml/jax/ |
Keywords: | deep-learning google jax machine-learning xla |
Licenses: | Apache |
Groups: | jax |
Submitter: | daskol |
Maintainer: | daskol |
Last Packager: | daskol |
Votes: | 7 |
Popularity: | 0.52 |
First Submitted: | 2021-01-12 12:50 (UTC) |
Last Updated: | 2024-10-23 00:00 (UTC) |
Dependencies (10)
- python-absl
- python-flatbuffers (python-flatbuffers-gitAUR)
- python-ml-dtypes
- python-numpy (python-numpy-flameAUR, python-numpy-gitAUR, python-numpy1AUR, python-numpy-mkl-binAUR, python-numpy-mklAUR, python-numpy-mkl-tbbAUR)
- python-scipy (python-scipy-gitAUR, python-scipy-mklAUR, python-scipy-mkl-tbbAUR, python-scipy-mkl-binAUR)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-wheel (make)
Required by (4)
- python-jax
- python-jax-bin
- python-safetensors (check)
- python-safetensors (optional)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
daskol commented on 2023-09-26 15:03 (UTC)
@segin No, it is not fix. In this case
jax.version.__version__
is not$pkgver
. Initial intent was to catch dirty releases since lately many packagers ranging from huggingface to google changes release pipelines, way how to version is assigned to package, or makes unfortunate mistakes. If release version is$pkgver
then the package must expose the same version$pkgver
consistently.segin commented on 2023-09-26 14:53 (UTC) (edited on 2023-09-26 14:54 (UTC) by segin)
Here's a ONE CHARACTER fix for this bug:
Replace the dash (-) between the package version and the wildcard with a period (.)
In my case, the generated wheel filename is jaxlib-0.4.16.dev20230926-cp311-cp311-manylinux2014_x86_64.whl but the wildcard is trying for jaxlib-0.4.16-*.whl
Right there in the wildcard after the 16 is a - when it should be a .
There, fixed by changing one single byte in the PKGBUILD.
daskol commented on 2023-09-24 13:03 (UTC)
@h3ss I see. I guess the issue is that
jaxlib
is built withbazel
. Its build directory actually is in~/.cache/bazel
and it is not cleans withmakepkg -C
. I'll try to move~/.cache/bazel
in$srcdir
in the future.h3ss commented on 2023-09-24 12:58 (UTC)
Thanks @daskol! That did the trick, now it builds the wheel as
src/jax-jaxlib-v0.4.16/dist/jaxlib-0.4.16-cp311-cp311-manylinux2014_x86_64.whl
and makepkg can find it.Not sure why, but even a cleanbuild with yay wasn't enough, I had to clone from AUR and
makepkg -si
manually, but when I did it worked just fine.daskol commented on 2023-09-23 13:25 (UTC)
@h3ss Finally, I've fixed the issue. There was a typo in
JAXLIB_RELEASE
envvar. 😔h3ss commented on 2023-09-23 02:51 (UTC) (edited on 2023-09-23 02:53 (UTC) by h3ss)
@daskol
I tried flushing the cache, building with a different AUR helper (yay vs paru) and also doing a git clone from the AUR and makepkg -si, the transcript of which you can see here:
https://pastebin.com/EesEmx94
In all circumstances, I get the same error. This goes for the python-jaxlib-cuda package as well. To be clear, the wheel does build successfully, it just doesn't finish making the package because the file name of the wheel doesn't match what makepkg expects it to be.
Could you clarify what the expected wheel file name is? What is the wheel file name when you build it in your environment?
daskol commented on 2023-09-22 16:07 (UTC)
@h3ss BTW I'm not sure but still. Have you tried to flush build cache? I'll try to build from scratch once again after a while.
h3ss commented on 2023-09-22 15:14 (UTC)
@daskol I'm sorry to report that I'm still encountering the same issue. The wheel file created is:
But the PKGBUILD is looking for
jaxlib-0.4.16-*.whl
:daskol commented on 2023-09-22 10:36 (UTC) (edited on 2023-09-22 10:44 (UTC) by daskol)
@toyan @h3ss Fixed and tested in clean room. Somehow envvars leaked in build time.
« First ‹ Previous 1 2 3 4 5 6 Next › Last »