Conversation
|
@sbo-bot: build x86_64 libraries/pytorch |
reverse dependencies - libraries/pytorchNone |
✅ sbolint - libraries/pytorch ✅ |
buildpkg x86_64 libraries/pytorchSnipped Build FailureDetails |
|
@sbo-bot: build x86_64 libraries/pytorch |
buildpkg x86_64 libraries/pytorchSnipped Build FailureDetails |
|
@sbo-bot: build x86_64 libraries/pytorch |
buildpkg x86_64 libraries/pytorchSnipped Build FailureDetails |
|
@sbo-bot: build x86_64 libraries/pytorch |
buildpkg x86_64 libraries/pytorchSnipped Build FailureDetails |
|
@cwilling are you familiar with pytorch? |
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
|
@sbo-bot: build x86_64 libraries/pytorch |
buildpkg x86_64 libraries/pytorchSnipped Build FailureDetails |
|
@aclemons this is strange |
No, I've heard of it but never tried using it. Interestingly, its homepage states one of its uses as: yet the SlackBuild's README includes: which makes me wonder what it's good for |
|
Building locally, I found numactl is also required. However this build then failed with: |
|
i guess we have to stick with the current version in repo or remove it if there's no solution build it under 15.0 |
|
From pytorch release notes for version 2.9: so looks like 2.8.0 (Aug 7, 2025) is the latest that might work - a bit better than existing 2.5.1(Oct 30, 2024) |
|
I have an almost successful build of 2.8.0 - compilation is complete but fails at SlackBuild line Any ideas? |
|
I spent a bit of time on it and couldn't make it work. Lastly I tried going back to the existing 2.5.1 version and it died with exactly the same problem - all the compiled stuff compiles OK but the python install step bombs out. I wonder if it ever worked? The 2.5.1 version was submitted nearly 2 years ago (Nov 24) but I don't think the 15.0 environment has changed a lot in that time. I think we should remove it if the maintainer can't show us how to make it build (any version on stable). |
|
Let me have a quick look. The last time we built it on the build box was in Feb (and we have built it 25 times it seems): find packages -type d -name pytorch -exec ls -la {} +
total 56852
drwxr-xr-x 2 root root 4096 Feb 21 2026 .
drwxr-xr-x 1336 root root 36864 Aug 24 02:31 ..
-rw-r--r-- 1 root root 135 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.dep
-rw-r--r-- 1 root root 1523459 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.lst
-rw-r--r-- 1 root root 534 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.meta
-rw-r--r-- 1 root root 293 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.txt
-rw-r--r-- 1 root root 56621304 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.txz
-rw-r--r-- 1 root root 66 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.txz.md5
-rw-r--r-- 1 root root 98 Feb 21 2026 pytorch-2.5.1-x86_64-25_SBo.txz.sha256 |
|
@aclemons I don't suppose we still have a build log for that last build do we? Or PR/MR from which it was done? I'd like to see what is different in my builds (one in container, other in full VM) which consistently fail with the same error. |
|
Unfortunately I don't keep all the build logs. Those last rebuilds would have just been for updated dependencies triggering a rebuild. The initial submission was here #8665 |
Yes I found that earlier today but no build log 😢 |
No description provided.