The _build_cpu
and _build_cuda
could be gotten from some global variables if set, and fallback to package default values. It's inconvenient to set the values every time in PKGBUILD.
Or could be split into two packages, depends on need of CUDA.
Git Clone URL: | https://aur.archlinux.org/python-dlib.git (read-only, click to copy) |
---|---|
Package Base: | python-dlib |
Description: | Dlib is a general purpose cross-platform C++ library designed using contract programming and modern C++ techniques. |
Upstream URL: | http://www.dlib.net/ |
Licenses: | boost |
Submitter: | fzavan |
Maintainer: | petronny (AutoUpdateBot) |
Last Packager: | petronny |
Votes: | 14 |
Popularity: | 0.180452 |
First Submitted: | 2016-10-27 15:05 (UTC) |
Last Updated: | 2024-07-19 13:18 (UTC) |
The _build_cpu
and _build_cuda
could be gotten from some global variables if set, and fallback to package default values. It's inconvenient to set the values every time in PKGBUILD.
Or could be split into two packages, depends on need of CUDA.
The CUDA version cannot be built as of cuda 12.5.0-1 that remove the symlinks hardcoded for CUDA compilers in the PKGBUILD.
See: https://gitlab.archlinux.org/archlinux/packaging/packages/cuda/-/issues/8
I got around the issue by removing the hardcoded environment variables from lines 44-48 of the PKGBUILD
Came here from howdy install errors. Had to build and install python-dlib
manually. Do yay -G python-dlib
and edit PKGBUILD
.
Then set _build_cpu
to 1 and _build_cuda
to 0 (unless you have an nvidia gpu then set to 1). Also edit options to options=(... !lto)
. Then compile with makepkg -si
.
Hope this helps anyone.
For some reason most recent version wants to compile it with CUDA even tho I am on an AMD system. I have python-dlib not python-dlib-cuda installed.
The options=(!lto)
setting in a PKGBUILD always overrides the LTO switch for that particular build, regardless of what any makepkg.conf
contains.
Set _build_cpu
and _build_cuda
to 1 and 0 to build or not build the CPU or CUDA version.
If options=(!lto)
has no effect, please check if it's still enabled in /etc/makepkg.conf
.
@petronny Please update the PKGBUILD as pointed out by Encrypt-Keeper.
Disabling LTO in /etc/makepkg.conf gets rid of the error. Thanks.
@ndoskrnl You seem to be mistaken, I'm not the maintainer, and it appears that this doesn't resolve the issue for some users.
I can confirm the issue with being unable to build due to the error generated with LTO version 12.0 instead of the expected 13.0 compilation terminated:
Uncommenting options=(!lto)
in the PKGBUILD has no effect. Still fails with the same error.
Editing /etc/makepkg.conf and replacing
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge debug lto)
with
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug !lto)
Allowed me to successfully build the package.
Pinned Comments
petronny commented on 2024-03-30 13:11 (UTC) (edited on 2024-03-30 13:13 (UTC) by petronny)
Set
_build_cpu
and_build_cuda
to 1 and 0 to build or not build the CPU or CUDA version.If
options=(!lto)
has no effect, please check if it's still enabled in/etc/makepkg.conf
.petronny commented on 2023-11-28 04:57 (UTC)
Prebuilt binaries of this package can be found in arch4edu.