@freecorndogs
I think yes, one way to verify is /usr/lib/libalpm.so should link to libalpm.so.13, if it is libalpm.so.12 you are on the older version
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: | 975 |
Popularity: | 22.62 |
First Submitted: | 2020-10-19 00:43 (UTC) |
Last Updated: | 2024-09-20 18:50 (UTC) |
« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 Next › Last »
@freecorndogs
I think yes, one way to verify is /usr/lib/libalpm.so should link to libalpm.so.13, if it is libalpm.so.12 you are on the older version
I am also getting the error
error: failed to run custom build command for
alpm v2.0.0
this version of alpm.rs does not support libalpm v12.0.2 only v13.x.0 is supported
My guess is that it's due to I'm running Manjaro and libalpm is a version behind?
With 1.7 I get Failed to find OpenSSL development headers.
openssl is installed.
@m040601 Your base system is out of date. Run pacman -Syu
(or paru --repo -Syu
if you still have a previous version working) to get your base system updated first, then it will build and run fine using the commands you showed.
Rather CARGO_MAKEFLAGS
Shouldn't RUSTFLAGS be used for that?
Could we extract -j N
from MAKEFLAGS
and pass to cargo
?
Check out my solution for scons
:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=boost-python2#n38
local JOBS; JOBS="$(grep -oP -- "-j\s*[0-9]+" <<< "${MAKEFLAGS}")" || JOBS="-j1"
cargo build "${JOBS}" --locked --features "${_features:-}" --release --target-dir target
v1.7 not building, got this error:
error: failed to run custom build command for `alpm v2.0.0`
Confirming that 1.7.0 works for me as well. It builds without a hitch and installs properly. Running and updating works as well. Built from git clone.
@m040601: Version 1.7.0 has been released and works for me
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