Arch Linux User Repository

yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory

This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay

pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

I cannot delete the spam comments appearing regularly in this page, which has also led me to disable notifications from here. I remind that the best way to receive support or report a problem is through the Upstream URL.

@destroydlolo -mno-omit-leaf-frame-pointer was added to makepkg.conf by pacman on archlinux arm during the upgrade from pacman 6.0.2 to 6.1.0 Perhaps your system broke when you handled a makepkg.conf.pacnew file some time after upgrading pacman. As far as I know, -mno-omit-leaf-frame-pointer is valid for all aarch64 but not for any 32-bit arm such as armv7. I don't use archlinux on arm, but you might want to report that issue upstream.

Thanks to Owndampu from reddit, the problem is from my /etc/makepkg.conf.

As bit strange as I was able to install other packages from sources without this issue.

Hi,

Installing Yay on an ARM7h SBC.

git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

failed with following messages :

==> Extracting sources...
  -> Extracting yay-12.4.2.tar.gz with bsdtar
==> Starting build()...
go build -trimpath -mod=readonly -modcacherw -ldflags '-X "main.yayVersion=12.4.2" -X "main.localePath=/usr/share/locale/" -linkmode=external -compressdwarf=false' -buildmode=pie -o yay
go: downloading github.com/Jguer/aur v1.2.3
go: downloading github.com/Jguer/go-alpm/v2 v2.2.2
go: downloading github.com/Jguer/votar v1.0.0
go: downloading github.com/Morganamilo/go-srcinfo v1.0.0
go: downloading github.com/deckarep/golang-set/v2 v2.6.0
go: downloading github.com/leonelquinteros/gotext v1.5.2
go: downloading golang.org/x/sys v0.18.0
go: downloading github.com/Morganamilo/go-pacmanconf v0.0.0-20210502114700-cff030e927a5
go: downloading github.com/adrg/strutil v0.3.1
go: downloading github.com/hashicorp/go-multierror v1.1.1
go: downloading golang.org/x/term v0.18.0
go: downloading golang.org/x/text v0.14.0
go: downloading github.com/hashicorp/errwrap v1.1.0
go: downloading github.com/itchyny/gojq v0.12.14
go: downloading github.com/mitchellh/mapstructure v1.5.0
go: downloading github.com/ohler55/ojg v1.21.4
go: downloading github.com/itchyny/timefmt-go v0.1.5
# runtime/cgo
armv7l-unknown-linux-gnueabihf-gcc: error: unrecognized command-line option '-mno-omit-leaf-frame-pointer'; did you mean '-fno-omit-frame-pointer'?
distcc[32361] ERROR: compile (null) on localhost failed
make: *** [Makefile:114: yay] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

Then, I did manual compilation :

cd src/yay-12.4.2
go build -trimpath -mod=readonly -modcacherw -ldflags '-X "main.yayVersion=12.4.2" -X "main.localePath=/usr/share/locale/" -linkmode=external -compressdwarf=false' -buildmode=pie -o yay

Which is succeeded. In I did another makepkg -siL --needed from the top directory and the installation succeded.

I'm not enough confident with makepkg to understand why it included this x86 option while running makepkg and not using direct go compilation.

Any tip welcome in case it happened again with other packages.

Thanks

Missing dependency to "less".

FYI, this built fine and I've been using it without problems for a little over a week on powerpc64le architecture.

@Locutus64 there was an update to pacman recently so you might have to rebuild yay.

I just ran Topgrade to do some updates that garuda-update doesn't do and Sonarr and Radarr had updates and after building the files I got the message "Yay exited with error code 1". I have no idea what is up with that cause Yay has been performing perfectly. I thought it might be a issue with the particular updates so I ran pikaur -S radarr-develop sonarr-develop and no issues at all.

Garuda Linux completely up to date Yay version 12.4.2-1

Hello, can you please tell me if this package works now?

@titandino may be, you need to replace /etc/resolv.conf with systemd-resolved stub symlink.

ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

https://wiki.archlinux.org/title/Systemd-resolved#DNS

Yeah I'm also getting connection refused on the proxy.golang.org package queries when updating. I can download them manually with CURL on the same addresses that are refusing to connect during the update stage too which is odd.