Package Details: ironclaw-git 0.16.1.r52.gab0a2e0-2

Git Clone URL: https://aur.archlinux.org/ironclaw-git.git (read-only, click to copy)
Package Base: ironclaw-git
Description: OpenClaw-inspired Rust personal AI assistant focused on privacy and security
Upstream URL: https://github.com/nearai/ironclaw
Licenses: Apache-2.0 OR MIT
Conflicts: ironclaw
Provides: ironclaw
Submitter: csmantle
Maintainer: csmantle
Last Packager: csmantle
Votes: 1
Popularity: 0.44
First Submitted: 2026-03-09 15:05 (UTC)
Last Updated: 2026-03-15 03:41 (UTC)

Latest Comments

« First ‹ Previous 1 2

daweiy commented on 2026-03-12 17:41 (UTC)

Issue Summary: Linker errors when building with default Arch Linux LTO flags

  1. Linker Errors observed: The build fails during the linking stage with numerous "undefined symbol" errors. These primarily affect crates that utilize assembly or FFI, such as ring, wasmtime, and libsql-ffi. Examples include:

    • ld.lld: error: undefined symbol: ring_core_0_17_14__avx2_available
    • ld.lld: error: undefined symbol: wasmtime_setjmp_28_0_1
    • ld.lld: error: undefined symbol: sqlite3_wal_manager
  2. Change made: Added options=(!lto) to the PKGBUILD.

  3. Root Cause: On a pure Arch Linux distribution with default /etc/makepkg.conf settings, the environment variable LDFLAGS includes -flto=auto. This forces Link Time Optimization at the system level. Certain Rust crates (especially ring) contain assembly code or pre-compiled objects that are incompatible with the system's LTO when passed through makepkg's environment. Disabling the lto option in the PKGBUILD prevents these flags from being forced onto the cargo build process, allowing it to link correctly using Rust's internal build logic.