Arch Linux User Repository

Updated PKGBUILD here: https://gist.github.com/hcartiaux/b663ec44d958d81c601257cf561085c8

The current version of patch_order_5.1.9 contains more patches and has a different sha key. That's why the list of downloaded files from this PKGBUILD isn't complete any more and compiling fails (as mrshady already wrote).

makepkg --skipchecksums gets further but reports missing patch file autofs-5.1.9-Remove-mentioning-of-nonstrict-option-in-comment.patch Removed that line from patch_order_5.1.9 and removed file patch_order_5.1.9.sign (edit breaks PGP signature). I suppose I could have used --skippgpcheck... makepkg --skipchecksums -e will build the package. Seems to work. So... PGP signature in patch_order_5.1.9.sign matches patch_order_5.1.9 however the checksum in PKGBUILD does not match patch_order_5.1.9 and there is a mismatch between files listed in patch_order_5.1.9 and the *.patch files.

@ajacocks can confirm it doesn't compile for me either. I've a fresh arch installation. Could you please take a second look at the problem reported by @planetmarshall ? I really need autofs here. Will try to reproduce on docker in a while.

@ajacocks, my guess is that this file has been updated with a lot of new patches, which by the way have not (yet?) been uploaded in the source directory. The mtime on the file patch_order_5.1.9 is 04-Feb-2026 06:09.

@planetmarshall, My guess is that you have an out-of-date file, as I just verified that the package builds properly, and the hash matches for the patch_orger_5.1.9 file.

I am seeing

==> ERROR: One or more files did not pass the validity check!

From patch_order_5.1.9 ... FAILED

@gawity:

Yup, you're absolutely right, this is a bug in ALARM's pacman build. Sorry I didn't recognize that before. I'm a novice when it comes to Arch packaging.

I've submitted a PR to ALARM to get this fixed. So the only thing the autofs package needs is to add 'aarch64' 'armv7h' to arch.

PeteAnderson – but the initial CFLAGS and CXXFLAGS come from your own makepkg.conf, not from autofs. Are you saying that ArchARM's /etc/makepkg.conf includes an option that their own GCC doesn't recognize?

I got it to build on armv7 (RPi2) by stripping that invalid option. It installed and works great.

From 62780a4cee7f69d63392f32ee0f899ef7e237160 Mon Sep 17 00:00:00 2001
From: Pete Anderson <pete.the.anderson@gmail.com>
Date: Wed, 22 Oct 2025 10:03:47 -0400
Subject: [PATCH] support ARM platforms

---
 .SRCINFO | 2 ++
 PKGBUILD | 8 +++++++-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/.SRCINFO b/.SRCINFO
index d9489c2..24bb9ce 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -4,6 +4,8 @@ pkgbase = autofs
    pkgrel = 5.1
    url = https://www.kernel.org/pub/linux/daemons/autofs/
    arch = x86_64
+   arch = aarch64
+   arch = armv7h
    license = GPL2
    makedepends = libldap
    makedepends = krb5
diff --git a/PKGBUILD b/PKGBUILD
index e06f39a..daf8f40 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -10,7 +10,7 @@ pkgname=autofs
 pkgver=5.1.9
 pkgrel=5.1
 pkgdesc='A kernel-based automounter for Linux'
-arch=('x86_64')
+arch=('x86_64' 'aarch64' 'armv7h')
 url='https://www.kernel.org/pub/linux/daemons/autofs/'
 license=('GPL2')
 depends=('libxml2')
@@ -117,6 +117,12 @@ prepare() {
 build() {
   cd "${srcdir}/${pkgname}-${pkgver}"

+  if [[ $CARCH = armv7* ]]; then
+    # GCC for 32-bit ARM rejects -mno-omit-leaf-frame-pointer, so strip it out
+    CFLAGS=${CFLAGS// -mno-omit-leaf-frame-pointer/}
+    CXXFLAGS=${CXXFLAGS// -mno-omit-leaf-frame-pointer/}
+  fi
+
   ./configure --prefix=/usr \
    --sysconfdir=/etc/autofs \
    --sbindir=/usr/bin \
-- 
2.51.1.dirty