Arch Linux User Repository

Ok, thanks for info. I thought since there are many arm arch they don't all always work. package updated

..provide string for your chromebook.

I already did. BOTH my chromebook and my Raspberry Pi 2 are that "armv7h".

...ANY package HAS TO work after compilation on every architecture.

After years of compiling and using dozens of PKGBUILD's from the AUR that do work on ArchLinux ARM, are confirmed and supported by the developer on ARM this is what I can honestly tell you.

I've never seen a package that, for example, does compile on "armv7h" but does not compile on aarch64. Or compiles on "armv6h" but not compiles on "armv7h" etc..

First, just because many people make this mistake (I also did it before, that's why I changed it today) doesn't make it correct. gmnisrv-git was submitted after gmni-git, I assume the author followed my example and did the same mistake as me.

I used namcap on this package, and this was the output before: gmni-git E: ELF file ('usr/bin/gmni') found in an 'any' package. gmni-git E: ELF file ('usr/bin/gmnlm') found in an 'any' package. gmni-git E: ELF file ('usr/lib/libgmni.a') found in an 'any' package.

That's not how I compile. I use the standard AUR procedures. You don't seem to understand, nobody compiles on aur like that, but that what's ANY arch mean. If your binary is portable (for example: some golang binaries), or program doesn't compile at package time (python, java etc) you can put ANY, ANY package HAS TO work after compilation on every architecture.

I can confirm that I've been compiling and using this package for months in a Raspberry Pi 2 and an arm Chromebook. Please check if arm is universal for every ARM device. If it's not, provide string for your chromebook, I'll add armv7h and the chromebook one.

Arch Linux officially supports only x86_64, and I don't care much for other distro variants.

You can check how other PKGBUILD maintainers do it for example with, https://aur.archlinux.org/packages/gmnisrv-git. It uses arch=("any"). And the program is from the same upstream author as gmni-git, https://git.sr.ht/~sircmpwn/.

... if you compile this package on x86, copy it into arm machine, it won't work ...

That's not how I compile. I use the standard AUR procedures.

1. Download, check and edit the PKGBUILD, on the same machine where I'll be using it.
2. Run makepkg -s
3. sudo pacman -U XXX-compiled-package.gz

Can you confirm on which arch it works ?

I can confirm that I've been compiling and using this package for months in a Raspberry Pi 2 and an arm Chromebook.

If you still dont' want to use "any" use.

arch=('i686' 'pentium4' 'x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')

Meaning:

arm - universal ???
armv6h - Raspberry Pi Zero
armv7h - Raspberry Pi 1, 2
aarch54 - Raspberry Pi 4 and 3 (64 bits)

Like so many other C,Rust or Go packages, for example, https://aur.archlinux.org/packages/yay-git

@m040601, from the link you sent:

Otherwise, use 'any' for architecture independent packages.

C binaries aren't architecture independent, if you compile this package on x86, copy it into arm machine, it won't work Can you confirm on which arch it works? I'll add it into PKGBUILD.

Please do not do this:

-arch=("any")
+arch=('x86_64' 'i686')

Check the guidelines, https://wiki.archlinux.org/title/Arch_package_guidelines#Architectures

This is a C code program that compiles and runs perfectly in other architectures. As well as its dependency, BearSSL, https://bearssl.org/

We want to use it with ArchLinux ARM in Raspberry Pi's and chromebooks .

For this to be built in a clean chroot, PKGBUILD needs some adjustments.

arch=(x86_64)
makedepends=(git scdoc)
-optdepends=(scdoc)