Arch Linux User Repository

Thank you very much! Though I have rwx ownership of the drive, it is indeed ntfs formatted. Building it on my ext4 partition worked as intended :) I hadn't thought about that...

If I had to guess, I'd say you're attempting to build auracle on an ntfs or vfat filesystem and mounted it with a mode or fmask that disables the executable bit.

When build() starts, I get the following error:

meson.build:1:0: ERROR: Could not invoke sanity test executable: [Errno 13] Permission denied: '/media/hdd/arch/builds/auracle-git/src/auracle/build/meson-private/sanitycheckcpp.exe'.

Do I have to manually permit meson to perform the sanity test on the C++ compiler?

FYI, I was using auracle successfully under armv7 (RPi3, 32bit) and after switching to armv8/aarch64 (RPi3, 64bit) I was not able to build the package using gcc (took forever, nearly freezing the board and crashed at step 3/27), but it went smoothly with clang (export CXX=clang++ && makepkg -A).

Ah thanks! I forgot about that. I appreciate the help for something so simple :)

I can confirm - works fine with fmt-6. I was only rebuild package in ~/.cache/pacaur/auracle-git and install after with sudo pacman -U auracle-git-r287.93fd134-1-x86_64.pkg.tar.xz All work now.

Just like every other soname bump, it's up to you to rebuild AUR packages.

auracle has no problems building and linking against fmt-6

FWIW it looks like this breaks with the latest version of fmt installed. Using the old version:

$ pacman -Q --info fmt | rg Version
Version         : 5.3.0-1
$ auracle show q
# Maintainer: Fabien Dubosson <fabien.dubosson@gmail.com>

[...]
$ sudo pacman -Syu
[...]
Packages (1) fmt-6.0.0-1

Total Installed Size:  0.56 MiB
Net Upgrade Size:      0.01 MiB
[...]
$ auracle show git
auracle: error while loading shared libraries: libfmt.so.5: cannot open shared object file: No such file or directory

Installing the old version of fmt works:

$ sudo pacman -U /var/cache/pacman/pkg/fmt-5.3.0-1-x86_64.pkg.tar.xz

(FWIW version of auracle: auracle-git-r287.93fd134-1.)

Is there a reason for limiting this package to i686 and x86_64 architectures?

This is a binary package. The arch=('any') designation is reserved for scripts and such. Arch only supports i686 and x86_64 in the AUR. Use makepkg -A to ignore arch designations and attempt to build anyway. AUR helpers will never be officially supported.

Is there a reason for limiting this package to i686 and x86_64 architectures ? I just built it on ArchlinuxARM (running on a raspberry pi 3) and it works perfectly :)

I just replaced the arch line with arch=('any') in the PKGBUILD, but could/should have used arch=('armv7h')