Search Criteria
Package Details: python-jaxlib 0.6.0-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-2.0 |
Groups: | jax |
Submitter: | daskol |
Maintainer: | daskol |
Last Packager: | daskol |
Votes: | 8 |
Popularity: | 0.139886 |
First Submitted: | 2021-01-12 12:50 (UTC) |
Last Updated: | 2025-04-20 20:53 (UTC) |
Dependencies (9)
- python-absl
- python-ml-dtypes
- python-numpy (python-numpy-gitAUR, python-numpy1AUR, python-numpy-mkl-binAUR, python-numpy-mklAUR, python-numpy-mkl-tbbAUR)
- python-scipy (python-scipy-gitAUR, python-scipy-mkl-binAUR, python-scipy-mkl-tbbAUR, python-scipy-mklAUR)
- clang18 (make)
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
Required by (5)
- python-blackjax
- python-jax
- python-jax-bin
- python-safetensors (optional)
- python-safetensors-bin (optional)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »
daskol commented on 2023-12-13 14:40 (UTC) (edited on 2023-12-13 14:42 (UTC) by daskol)
@gatsby I see. I guess the issue is that AVX is a target architecture by default (in release configuration). Try to this patch.
Your machine is pretty oldie indeed. :)
FYI The issue is that
protoc
is shipped withjax
sources and is built from sources. With targeting newer hardwareprotoc
fails to run.gatsby commented on 2023-12-13 14:34 (UTC)
Thanks for the advice.
I have launched the command bazel-6.1.2-linux-x86_64 with the indicated parameters and internally it gives an error in another instruction
This executable ./bin/external/com_google_protobuf/protoc indicates that the instruction does not exist: SIGILL (Illegal instruction).
However, when I launch the default protoc installed on the machine it works.
I infer that it is because the CPU-enabled instruction set in the protoc binary that downloads.
I'm afraid that there is no easy way to solve this.
daskol commented on 2023-12-13 05:52 (UTC)
@gatsby Please attach long output as a file next time.
I've just checked in clean environemnt that
python-jaxlib
compiles without any issues. I guess that the first thing you should to do is to run command that fails.By the way, can you be sure that hdd/ssd is functioning properly if your compute is pretty old?
gatsby commented on 2023-12-11 09:17 (UTC)
Hello, I have an error in the compilation for which I cannot find information. The computer is old and has few resources, it may have something to do with it but there are no clues in the traces.
daskol commented on 2023-10-27 16:42 (UTC) (edited on 2023-10-27 16:50 (UTC) by daskol)
@mane.andrea I'm not sure that prepare/build is a bug. According to Arch Wiki
Envvars, indeed, should not be placed in
prepare()
. Anyway reporting an issue toyay
could be a good idea to highlight sharp bits once again.UPD I guess I know why
yay
runsprepare()
andbuild()
in different shell sessions:yay
prompts a user to edit or viewPKGBUILD
.Sorry for that. I don't know how it could happen.
mane.andrea commented on 2023-10-27 00:15 (UTC)
You accidentally pushed
in
.SRCINFO
. I found out when I saw my PKGBUILD was not up-to-date even after I had synced yay.mane.andrea commented on 2023-10-26 19:36 (UTC)
@daskol I think it's a good idea to submit a bug report to yay. Do you have any additional information that could be useful for the bug report? I.e. which is the specific part of the PKGBUILD that requires prepare and build be invoked sequentially? (Sorry if my understanding of the issue is superficial)
rekman commented on 2023-10-24 19:36 (UTC)
@daskol uggghhh....
daskol commented on 2023-10-24 19:32 (UTC)
@rekman Yes, it is. LLVM is transitive dependency via XLA and both XLA and LLVM are pinned by commit hashes. I tried to build with system's LLVM (bad idea).
daskol commented on 2023-10-24 19:30 (UTC)
@h3ss Indeed. @Henry-ZHR mentioned the issues regarding to
yay
. I consulted with some core packages andPKGBUILD
docs and it turns out thatprepare
andbuild
can be invoked separately in general. But some core packages ignore this rule sincemakepkg
in contrast toyay
runs all stages sequentially.« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »