Arch Linux User Repository

@benpiano800 I have added a libcpufeatures PKGBUILD for you to maintain. It uses the stable version of libcpufeatures instead of the git version. Please add the gtest dependency. Then the prepare step is not required and cmake will not download a copy of googletest.

your PKGBUILD needs fixing, this worked for me.

source=(
  "${_pkgname}::git+https://github.com/google/cpu_features.git#branch=main"
)

the change being that git disabled unauthorised downloads via git, so i chosed https ngl, am a little proud as this is my first time fixing/touching a pkgbuild

Should be fixed now

@Jolly_Roberts okay, will do. I'll credit you as a contributor for the suggestion.

This worked for me:

source=( "${_pkgname}::git+git://github.com/google/cpu_features.git#branch=main" )

o/

This is currently breaking cause the upstream re-named their primary branch to "main" and the PKGBUILD does not account for that. I think if you have it git checkout the 'main' branch before the call to cmake it would work.

Cloning into 'libcpufeatures'... done. warning: remote HEAD refers to nonexistent ref, unable to checkout.

==> Starting prepare()... CMake Error: The source directory "/home/jollyroberts/.cache/yay/libcpufeatures-git/src/libcpufeatures" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. ==> ERROR: A failure occurred in prepare(). Aborting... -> error making: libcpufeatures-git

Adopting because I use it and want to maintain it

Disowning, since I do not use it and dont want to maintain it.

@DHouk:

git log -n 1 --no-show-signature --format=tformat:%ci

I also do not have GPG keys. I do not know what goes on, maybe it is some issue with your local git configuration?

I have added it anyway. I do not understand what it does.

Iʼm getting an error when trying to get the latest version, because I do not have the GPG keys of everyone who might contribute to the upstream project. Maybe Iʼm missing something about how GPG is supposed to work, but it seems like signature verification is not needed here. Would changing the pkgbuild to skip GPG signature verification when getting the version cause security issues, and if so, is there a better fix?

diff --git i/PKGBUILD w/PKGBUILD
index 1519cbd..03b0a99 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -39,7 +39,7 @@ pkgver() {
   _subver="$(git describe --tags | awk -F'-' '{print $2}')"
   _rev="$(git rev-list --count HEAD)"
   _hash="$(git rev-parse --short HEAD)"
-  _date="$(git log -n 1 --format=tformat:%ci | awk '{print $1}' | tr -d '-')"
+  _date="$(git log -n 1 --no-show-signature --format=tformat:%ci | awk '{print $1}' | tr -d '-')"
   if [ -z ${_ver} ]; then
     error "Error in ${FUNCNAME[0]}: Version information could not determined."
     return 1