error: could not compile alpm
(lib) due to 1 previous error
on aarch64
Git Clone URL: | https://aur.archlinux.org/paru.git (read-only, click to copy) |
---|---|
Package Base: | paru |
Description: | Feature packed AUR helper |
Upstream URL: | https://github.com/morganamilo/paru |
Keywords: | AUR helper pacman rust wrapper yay |
Licenses: | GPL-3.0-or-later |
Submitter: | Morganamilo |
Maintainer: | Morganamilo |
Last Packager: | Morganamilo |
Votes: | 1025 |
Popularity: | 18.35 |
First Submitted: | 2020-10-19 00:43 (UTC) |
Last Updated: | 2024-09-20 18:50 (UTC) |
error: could not compile alpm
(lib) due to 1 previous error
on aarch64
I was transitioning from yay to paru and thus used yay to install paru (but I don't believe this changes the error that I experienced). Since I didn't have cargo installed at the moment, running the command asked me what version of rust to install and I chose rustup, which leads to the following error:
==> Making package: paru 2.0.4-1 (Mon 05 May 2025 09:19:41 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found paru-2.0.4.tar.gz
==> Validating source files with sha256sums...
paru-2.0.4.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting paru-2.0.4.tar.gz with bsdtar
==> Starting prepare()...
error: rustup could not choose a version of rustc to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.
error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.
==> ERROR: A failure occurred in prepare().
Aborting...
-> error making: paru-exit status 4
-> Failed to install the following packages. Manual intervention is required:
paru - exit status 4
I expect the build to run without requiring manual intervention, but I will admit having to install cargo first is not much of a big ask anyways
It builds and runs fine on powerpc
, powerpc64
, and powerpc64le
as well as riscv64
. Adding all 4 of these architectures to the arch
array would be appreciated.
@Morganamilo would you mind adding riscv64
to the arch
array?
Worked great... no issues with at all, with the installation.
Ehi why do you download zip files? Should not we download directly the git repository?
The following changes fixed the build on my aarch64 systems today:
diff --git a/PKGBUILD b/PKGBUILD
index f503694..6289b7e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,6 +9,7 @@ backup=("etc/paru.conf")
arch=('i686' 'pentium4' 'x86_64' 'arm' 'armv7h' 'armv6h' 'aarch64')
license=('GPL-3.0-or-later')
makedepends=('cargo')
+makedepends_aarch64=('cargo' 'clang')
depends=('git' 'pacman' 'libalpm.so>=14')
optdepends=('bat: colored pkgbuild printing' 'devtools: build in chroot and downloading pkgbuilds')
sha256sums=('b9c67f1390caacc949c2eb2a254e8cf37778f382c3c6b8d057fa6feb6eaeb0f9')
@@ -29,6 +30,10 @@ build () {
export CARGO_PROFILE_RELEASE_LTO=off
fi
+ if [[ $CARCH = aarch64 ]]; then
+ _features+="generate,"
+ fi
+
cargo build --frozen --features "${_features:-}" --release --target-dir target
./scripts/mkmo locale/
}
This doesn't built on arm. Please see this github issue https://github.com/Morganamilo/paru/issues/1154. The "generate" feature should be enabled when building aarch64 or armv7h.
Also clang should be a dependency.
I had the issue with the libalpm.so and it was that the mirror I was using that was out of sync (per https://archlinux.org/mirrors/status/ ) . After updating the mirror and updating, the newer libalpm was available.
@wag Thank you -- that clears things up for me. I'm on Endeavour OS, and happy to be patient. But this fact was not clear in the below comments. I'll look forward to the update and be glad to have paru working again!
Pinned Comments
haxie commented on 2023-05-26 17:45 (UTC)
you're better off contacting her via the github, this comments section is 90% "it's out of date" from people who didn't scroll down before posting