Arch Linux User Repository

Again like I complained about back in March, you are bumping this package without even test building it — that or your test builds are not being done on an up to date Arch system with current makepkg default configs and current compiler versions. This does not build and will not build in a clean chroot with current Arch defaults until you fix (or at my suggestion, gut out) the incomplete clang overrides. It builds fine with GCC and the optimized Rust profile stiff in the patch in my previous comment.

The CFLAGS munging in this PKGBUILD is absolute wonkery. Please ditch it entirely. Substituting a half-baked clang alternative is not an improvement if you don't actually set it up properly. This is now completely broken because of upstream changes in Arch's default flags (as is apt to happen from time to time).

Here is some proper build time optimizations for Rust packages in Arch. This can be applied with git am < lto.patch (make sure the patch file has the trailing blank line!):

From 6653bf1e797653e3913777bc6a0808fa88598a97 Mon Sep 17 00:00:00 2001
From: Caleb Maclennan <caleb@alerque.com>
Date: Fri, 3 Jul 2026 19:10:09 +0300
Subject: [PATCH] Drop clang hacks and enable gcc LTO

Signed-off-by: Caleb Maclennan <caleb@alerque.com>
---
 PKGBUILD | 25 +++++++------------------
 1 file changed, 7 insertions(+), 18 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 993c668..0399f4f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,29 +9,18 @@ url="https://github.com/AlexsJones/llmfit"
 license=('MIT')

 depends=('glibc')
-makedepends=('git' 'rust' 'cargo' 'clang')
+makedepends=('git' 'cargo')

 source=("git+https://github.com/AlexsJones/llmfit.git#tag=v${pkgver}")
 sha256sums=('f870e1e9df13ba90244fcb9527f1bf36d84243f9ecf218fe174923220ecc71f0')

 _setup_build_env() {
-  export CC=clang
-  export CXX=clang++
-
-  case " ${CFLAGS:-} " in
-    *" -ffat-lto-objects "*) ;;
-    *) export CFLAGS="${CFLAGS:+${CFLAGS} }-ffat-lto-objects" ;;
-  esac
-
-  case " ${CXXFLAGS:-} " in
-    *" -ffat-lto-objects "*) ;;
-    *) export CXXFLAGS="${CXXFLAGS:+${CXXFLAGS} }-ffat-lto-objects" ;;
-  esac
-
-  case " ${RUSTFLAGS:-} " in
-    *" -Clinker=clang "*) ;;
-    *) export RUSTFLAGS="${RUSTFLAGS:+${RUSTFLAGS} }-Clinker=clang" ;;
-  esac
+  CFLAGS+=' -ffat-lto-objects'
+  export CARGO_PROFILE_RELEASE_DEBUG=2
+  export CARGO_PROFILE_RELEASE_STRIP=false
+  export CARGO_PROFILE_RELEASE_LTO=true
+  export CARGO_PROFILE_RELEASE_CODEGEN_UNITS=1
+  export CARGO_PROFILE_RELEASE_OPT_LEVEL=3
 }

 prepare() {
-- 
2.55.0

@arcpie Please do not use SKIP for the checksum of a stable release package. Combined with the #tag=v$pkgver as part of your source URL, Arch's tooling will in fact compute a stable checksum for Git based sources. Please use updpkgsums to fetch and set the current sum in the PKGBUILD then makepkg --printsrcinfo > .SRCINFO and get those changes published.

Additionally if you add this file as .nvchecker.toml to the repo, users and yourself can use pkgctl version update to bump the PKGBUILD to the current version on demand:

[llmfit]
source = "git"
git = "https://github.com/AlexsJones/llmfit.git"
prefix = "v"

@SteamedFish thanks for the feedback! added both clang and clang++ vars, also added clang as makedep.@alerque added the lto fix, aslo i've added a test build phase to make sure the build environment is clean from my local packages and it now builds succesfully anywhere. Thanks to both of you

@SteamedFish thanks for the feedback! added both clang and clang++ vars, also added clang as makedep.@alerque added the lto fix, aslo i've added a test build phase to make sure the build environment is clean from my local packages and it now builds succesfully anywhere. Thanks to both of you

This package fails to link with GCC (the default). Please add clang to makedepends and set the compiler in the build() function: export CC=clang CXX=clang++

Also, please add 'aarch64' to the arch array. I've verified it builds successfully on ARM64 with Clang (GCC fails with the same linking errors as on x86_64).

@arcpie Whether or not it builds for you is going to depend on your host system and a lot of other variables. You likely are not even building with LTO flags enabled at all. The only way to properly check if the packaging is correct or not is to build it in a chroot build environment with the default Arch build environment options, and it does not build in a chroot without the LTO fix. This is a well established problem affecting hundreds of Arch packages, official and AUR alike. You can see it in the PKGBUILD for many official packages

@alerque hmm it does build for me, i have a final tomorrow so i wont be able to look into it rn but tomorrow ill check it

Gah! Please stop the bot from pushing version bumps that don't even build. This package has the classic issue with the ring crate that won't compile with LTO enabled and needs CFLAGS+=' -ffat-lto-objects'.

@alerque thanks for the correction, I've created llmfit-bin and updated this package so it builds from source