Search Criteria
Package Details: leela-zero 0.17-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/leela-zero.git (read-only, click to copy) |
---|---|
Package Base: | leela-zero |
Description: | Go engine with no human-provided knowledge, modeled after the AlphaGo Zero paper. |
Upstream URL: | https://github.com/leela-zero/leela-zero |
Licenses: | GPLv3 |
Submitter: | apetresc |
Maintainer: | apetresc (algebro) |
Last Packager: | apetresc |
Votes: | 6 |
Popularity: | 0.057831 |
First Submitted: | 2018-04-25 03:12 (UTC) |
Last Updated: | 2019-04-04 19:46 (UTC) |
Dependencies (10)
- boost (boost-gitAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- openblas (openblas-lapackAUR)
- opencl-driver (opencl-nvidia-410xxAUR, amdapp-sdkAUR, opencl-nvidia-340xxAUR, opencl-nvidia-440xxAUR, vc4cl-gitAUR, opencl-nvidia-430xxAUR, opencl-legacy-amdgpu-proAUR, intel-compute-runtime-gitAUR, beignetAUR, opencl-nvidia-vulkanAUR, beignet-gitAUR, intel-openclAUR, clvk-gitAUR, opencl-rusticl-mesa-minimal-gitAUR, mesa-gitAUR, mesa-wsl2-gitAUR, opencl-nvidia-535xxAUR, opencl-nvidia-525xxAUR, opencl-510xx-nvidiaAUR, opencl-nvidia-470xxAUR, amdonly-gaming-opencl-clover-mesa-gitAUR, amdonly-gaming-opencl-rusticl-mesa-gitAUR, opencl-nvidia-550xxAUR, opencl-nvidia-390xxAUR, opencl-nvidia-teslaAUR, opencl-amdAUR, intel-compute-runtime-binAUR, opencl-nvidia-betaAUR, intel-compute-runtime-legacy-binAUR, intel-compute-runtime-legacyAUR, intel-compute-runtime, intel-oneapi-compiler-shared-runtime, opencl-clover-mesa, opencl-nvidia, opencl-rusticl-mesa, rocm-opencl-runtime)
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- ocl-icd (khronos-ocl-icd-gitAUR, khronos-ocl-icdAUR) (make)
- opencl-headers (opencl-headers-gitAUR) (make)
Latest Comments
1 2 3 Next › Last »
MarsSeed commented on 2023-07-02 10:34 (UTC)
Please check the changes around Arch openblas and blas-openblas. You might need to switch depends from
openblas
toblas-openblas
. Arch openblas package is incomplete, only blas-openblas carries the full OpenBlas Lapack suite.Background:
Arch announced on June 14, 2023 a new blas-openblas repo package, which finally offers the full suite of OpenBLAS Lapack, with their blas implementation and corresponding cblas/lapacke interfaces.
apetresc commented on 2020-02-19 17:29 (UTC)
@jshholland Can you try a clean build? I can no longer reproduce the problem on 5.2.1, it's all good on my end.
jshholland commented on 2020-02-19 17:11 (UTC)
According to the pacman NEWS file, the gzip bug was fixed in 5.2.0, but I'm still seeing this same bug.
apetresc commented on 2019-09-19 18:37 (UTC)
@UndeadKernel: Ah, figured it out! Eli Schwartz confirmed on IRC that it's a recently-introduced upstream bug: https://git.archlinux.org/pacman.git/commit/?id=99c5809bbf01725829ce67458565b46bce32eaa9
It's fixed in pacman-git but hasn't been released in pacman yet. Once it's released, it will restore the old auto-extraction behaviour.
Given that circumstance, I'm not gonna push a hotfix, since I'd have to just revert it soon once Pacman is updated
apetresc commented on 2019-09-19 18:28 (UTC)
@UndeadKernel: Hmm, you're right, something has clearly changed in makepkg, this exact PKGBUILD (plus leela-zero-git's almost-identical one) definitely used to work as-is a few weeks ago.
I think makepkg used to implicitly extract *.gz resources and now it doesn't anymore. I'll try to get to the bottom of this before just pushing out a hotfix.
UndeadKernel commented on 2019-09-18 09:42 (UTC)
I'm observing an error while installing:
I don't see anywhere in the PKGBUILD where the
weights.txt.gz
file is uncompressed. Am I missing something obvious?apetresc commented on 2019-08-05 17:53 (UTC)
@janwil You will have more luck posting your findings so far in the ticket linked by @Liso; it's likely this is just a bug with Leela-Zero itself, not this particular package of it.
(You might also want to give leela-zero-git a try, just in case whatever the problem is has already been fixed. Leela-Zero is very slow to tag actual releases, so this is not too unlikely)
Hope that helps!
janwil commented on 2019-08-04 14:03 (UTC)
@Liso, I can confirm that my results of 'coredump gdb' and 'where' are similar to yours. What does this mean now and what can I do to fix this? Is there anything I can do in the first place? I am unfortunately not very good at debugging and fixing C++ myself :(
Best regards, Jan
Liso commented on 2019-07-28 17:57 (UTC)
Now I found that it is same as this issue https://github.com/leela-zero/leela-zero/issues/2438
1 2 3 Next › Last »