Arch Linux User Repository

Thanks Dan39, I have updated the package now with your suggestion. I'm also able to build the package successfully in a clean environment now.

Trying to build this fails now since cmake 4.0 release, with error shown below. I got around this for now by adding -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to the cmake line in the PKGBUILD. It is caused by the CMakeLists.txt files containing cmake_minimum_required(VERSION 2.8). The cmake docs now say Changed in version 4.0: Compatibility with versions of CMake older than 3.5 is removed. Calls to cmake_minimum_required(VERSION) or cmake_policy(VERSION) that do not specify at least 3.5 as their policy version (optionally via ...<max>) will produce an error in CMake 4.0 and above.

==> Starting build()... 
CMake Error at CMakeLists.txt:3 (cmake_minimum_required): 
 Compatibility with CMake < 3.5 has been removed from CMake.

 Update the VERSION argument <min> value. Or, use the <min>...<max> syntax 
 to tell CMake that the project requires at least <min> but has been updated 
 to work with policies introduced by <max> or earlier.

 Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. 


-- Configuring incomplete, errors occurred! 
==> ERROR: A failure occurred in build(). 
 Aborting... 

Thanks for the feedback @eclairevoyant. I have fixed the package now.

gcc, make, and pkgconfig should be removed from the makedepends as they are part of base-devel as per https://wiki.archlinux.org/title/PKGBUILD#makedepends:

The package base-devel is assumed to be already installed when building with makepkg. Dependencies of this package should not be included in makedepends array.

the update to libusb 1.0.25 exposed a bug in the airspyhf driver.

https://github.com/libusb/libusb/issues/1059

patch supplied https://github.com/jj1bdx/airspyhf/commit/c55a305a79eea70cf61ea22a081b29d37805b9fc

hopefully airspy accepts it soon.

@dc0sk Sorry for the late response. I have now added aarch64 to the arch list.

Would you be so kind and add 'aarch64' to the PKGBUILD? I tested it on a pi4 and it works like a charm.

To solve the issues with the pre-systemd gid-based device access, you should modify the /etc/udev/rules.d/52-airspyhf.rules from
ATTR{idVendor}=="03eb", ATTR{idProduct}=="800c", SYMLINK+="airspyhf-%k", MODE="660", GROUP="plugdev"

to
ATTR{idVendor}=="03eb", ATTR{idProduct}=="800c", SYMLINK+="airspyhf-%k", MODE="660", TAG+="uaccess"

This is the way to go with systemd. For reference, please see:
https://wiki.archlinux.org/index.php/users_and_groups#Pre-systemd_groups
https://wiki.archlinux.org/index.php/Talk:Udev#Use_of_.27uaccess.27_instead_of_GROUP_and_MODE.3F

@aulavik Good to hear that you found the solution.

Found the solution to my own problem.

The udev file /etc/udev/rules.d/52-airspyhf.rules has an entry GROUP="plugdev".

I created the group plugdev, and added my username into.

Now it works without sudo, and gqrx can now detect the device.