php74

Category: local-install (rebuilt only so archlinuxaba/the cluster gets it too; not maintained/adapted/owned by us — see arch/scripts/install_only_packages). Split package (dozens of subpackages: php74-cli, php74-fpm, php74-gd, etc.) generated by the upstream arch-phpbs tool. Needed by php74-apcu and owncloud.

Build notes (2026-08-19)

• arch=("$CARCH") doesn’t work with our tooling. Upstream ships a dynamic self-resolving arch=() (an arch-phpbs generator trick, presumably meant for a build wrapper that re-invokes makepkg per target arch). repo_build.sh parses arch=(...) as literal text from the PKGBUILD file (sed -n 's/^arch=(\(.*\))$/\1/p'), so it read the literal string $CARCH – not a real arch – and would have built nothing. Fixed by replacing it with a real literal array, arch=('x86_64' 'i686' 'pentium4').
• Missing dependency: c-client. A hard makedepends (needed for the imap extension) that wasn’t available anywhere – not in official repos, not previously published to archlinuxaba, only on AUR. Built and published it first (see memory/c-client.md).
• Missing libtiff makedepend, only surfaced on 32-bit. The gd extension’s configure check failed with Package 'libtiff-4', required by 'gdlib', not found on i686/pentium4 (not x86_64) – archlinux32’s gd build apparently still links against libtiff where the current x86_64 gd doesn’t declare it in gdlib.pc. Fixed by adding libtiff to makedepends explicitly.
• pentium4 fails, GD symbols unlinkable. After the libtiff fix, pentium4’s configure got past the gdlib >= 2.1.0 check but then failed to link any basic GD symbol (gdImageCreate etc. all report “no” from the -lgd link test), with configure: error: GD build test failed. i686 (same gd package family) does NOT hit this – pentium4-chroot-specific. Not root-caused further; left pentium4 in arch=() per explicit user instruction (build/publish what works, don’t keep chasing it) – pentium4 will just show FAILED on every rebuild and get skipped, which repo_build.sh tolerates fine as long as other arches succeed.
• Self-inflicted stale-publish incident: a leftover, already-built pkgrel=11 artifact set (predating this session, before the arch=()/libtiff fixes bumped pkgrel to 11.1) was still sitting in the pkgdir on the first successful build attempt. Both the correct 11.1 and the stale 11 x86_64 packages got uploaded in the same run, and since repo-add is keyed by pkgname (last write wins, not highest version), the stale 11 ended up live, clobbering the fix. Caught by checking upload order in the log (grep -n "php74-cli-7.4.33-11") after the fact. Fixed with a second clean rebuild (pkgdir was already swept of old artifacts by repo_build.sh’s own untracked-file cleanup by then, so the retry only ever produced 11.1 files). Lesson: always check for and clean stale .pkg.tar.zst artifacts in a package’s dir before the first build of a session, not just when something looks wrong after the fact – a stale artifact can silently outrace a correct one through repo_publish.sh if pkgrel bumps didn’t fully clear the old file first.
• pkgrel "11" -> "11.1" (local-install, X.Y scheme; note this PKGBUILD holds pkgrel as a quoted string, not a bare integer – quoting still works fine with the X.Y scheme).
• End state: x86_64 and i686 publish cleanly (122 packages each: ~61 subpackages x {package, debug} roughly). pentium4 excluded (in arch=() but always fails, tolerated).