@friday13 I have removed yay using pacman -Rns yay. Then, when I'm trying to rebuild it using makepkg -si, the building step throw me an Aborting... because -Werror is used somewhere (makepkg -Cfsi give me the same result).
Search Criteria
Package Details: yay 12.5.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/yay.git (read-only, click to copy) |
|---|---|
| Package Base: | yay |
| Description: | Yet another yogurt. Pacman wrapper and AUR helper written in go. |
| Upstream URL: | https://github.com/Jguer/yay |
| Keywords: | arm AUR go helper pacman wrapper x86 |
| Licenses: | GPL-3.0-or-later |
| Submitter: | jguer |
| Maintainer: | jguer |
| Last Packager: | jguer |
| Votes: | 2326 |
| Popularity: | 27.01 |
| First Submitted: | 2016-10-05 17:20 (UTC) |
| Last Updated: | 2025-04-24 09:06 (UTC) |
Dependencies (5)
- git (git-gitAUR, git-glAUR)
- pacman (pacman-gitAUR)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, gcc-go) (make)
- doasAUR (opendoas-retryAUR, opendoas) (optional) – privilege elevation
- sudo (fake-sudoAUR, polkit-fakesudoAUR, sudo-gitAUR, doas-sudo-shimAUR, doas-sudo-shim-minimalAUR, sudo-hgAUR, fudo-gitAUR, sudo-selinuxAUR, sudo-rs-symlinkAUR) (optional) – privilege elevation
Required by (46)
- abinot
- aconfmgr-git (optional)
- arch-update (optional)
- arch-update-git (optional)
- archlink (optional)
- axu
- axu-bin
- blender-launcher-git
- checkupdatify
- cleanupdate-git (optional)
- cmd-not-found (optional)
- dpw (optional)
- etwas
- fuzzy-pkg-finder (optional)
- fzpac (optional)
- fzpac-git (optional)
- idos-package-updater-script
- klaus-bin
- meta-package-manager (optional)
- meta-package-manager-git (optional)
- octopi (optional)
- pac-util (optional)
- pac-util-git (optional)
- packup (optional)
- pacup-arch-git (optional)
- pak-bin
- pak-git
- parui (optional)
- parui-git (optional)
- paxs
- pcmn-git
- pipac (optional)
- pkg-listn (optional)
- pkg-listn-git (optional)
- pkgctrl-bin
- pkm
- plasma6-applets-arch-update-notifier (optional)
- pmm-git (optional)
- ppac-git (optional)
- repkg (optional)
- spm-arch
- ualsv
- uau (optional)
- update-notifier (optional)
- yay-faster-cn
- yayfzf
Sources (1)
Yatis commented on 2021-06-05 14:13 (UTC)
friday13 commented on 2021-06-05 13:00 (UTC)
jguer commented on 2021-06-03 19:36 (UTC)
@kseistrup please create an issue on https://github.com/Jguer/yay this issue may require more investigation than a simple reply (I think it's a gcc-go vs go issue)
Yatis commented on 2021-06-03 19:11 (UTC)
I also got a yay error yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory. And when I try to rebuild the package, I have some log errors:
go build -trimpath -mod=readonly -modcacherw -tags six -ldflags '-X "main.yayVersion=10.2.2.r5.g059ca9d" -X "main.localePath=/usr/share/locale/" -linkmode=external' -buildmode=pie -o yay
go: downloading github.com/Jguer/go-alpm/v2 v2.0.5
go: downloading github.com/Morganamilo/go-pacmanconf v0.0.0-20210502114700-cff030e927a5
go: downloading github.com/Morganamilo/go-srcinfo v1.0.0
go: downloading github.com/leonelquinteros/gotext v1.4.0
go: downloading github.com/mikkeloscar/aur v0.0.0-20200113170522-1cb4e2949656
go: downloading github.com/pkg/errors v0.9.1
go: downloading golang.org/x/term v0.0.0-20210503060354-a79de5458b56
go: downloading github.com/stretchr/testify v1.7.0
go: downloading golang.org/x/sys v0.0.0-20210507161434-a76c4d0a0096
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b
go: downloading github.com/davecgh/go-spew v1.1.1
# runtime/cgo
gcc_fatalf.c: In function ‘fatalf’:
gcc_fatalf.c:17:9: error: implicit declaration of function ‘fprintf’ [-Werror=implicit-function-declaration]
17 | fprintf(stderr, "runtime/cgo: ");
| ^~~~~~~
gcc_fatalf.c:11:1: note: include ‘<stdio.h>’ or provide a declaration of ‘fprintf’
10 | #include "libcgo.h"
+++ |+#include <stdio.h>
11 |
gcc_fatalf.c:17:9: error: incompatible implicit declaration of built-in function ‘fprintf’ [-Werror=builtin-declaration-mismatch]
17 | fprintf(stderr, "runtime/cgo: ");
| ^~~~~~~
gcc_fatalf.c:17:9: note: include ‘<stdio.h>’ or provide a declaration of ‘fprintf’
gcc_fatalf.c:19:9: error: implicit declaration of function ‘vfprintf’ [-Werror=implicit-function-declaration]
19 | vfprintf(stderr, format, ap);
| ^~~~~~~~
gcc_fatalf.c:19:9: note: include ‘<stdio.h>’ or provide a declaration of ‘vfprintf’
gcc_fatalf.c:22:9: error: implicit declaration of function ‘abort’ [-Werror=implicit-function-declaration]
22 | abort();
| ^~~~~
gcc_fatalf.c:11:1: note: include ‘<stdlib.h>’ or provide a declaration of ‘abort’
10 | #include "libcgo.h"
+++ |+#include <stdlib.h>
11 |
gcc_fatalf.c:22:9: error: incompatible implicit declaration of built-in function ‘abort’ [-Werror=builtin-declaration-mismatch]
22 | abort();
| ^~~~~
gcc_fatalf.c:22:9: note: include ‘<stdlib.h>’ or provide a declaration of ‘abort’
cc1: all warnings being treated as errors
make: *** [Makefile:112: yay] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I don't know who is the f** genius which use -Werror in production, but I'm not able to remove the cursed flags because I don't know where it is... Any idea ?
abdulhakeem commented on 2021-06-02 02:51 (UTC) (edited on 2021-06-02 02:53 (UTC) by abdulhakeem)
Got a yay update earlier today and then just got pacman 6 a few moments ago, and now i get this when running yay:
"yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory"
Assumed that yay's update earlier today was for pacman 6 but perhaps not lol. Will try jguer's pinned suggestion and rebuild yay
EDIT: rebuilding yay as per jguer's suggestion worked
kseistrup commented on 2021-06-01 08:29 (UTC)
go: parsing $GOFLAGS: non-flag "six"
What can I do about this?
mudkipscience commented on 2021-06-01 05:51 (UTC) (edited on 2021-06-01 05:53 (UTC) by mudkipscience)
Why was this flagged as out-of-date? You just need to reinstall yay manually to resolve the libalpm issues
edolnx commented on 2021-05-26 01:34 (UTC)
@marcelroed I had the same problem, downgraded to pacman 5.x instead of having a pacman 6 pre-release installed and it was fine.
jguer commented on 2021-05-20 11:41 (UTC)
With pacman 6 arriving a rebuild of yay will be necessary, if you upgrade pacman without upgrading yay at the same time, yay will not run after. I'm bumping the pkgrel so it shows up on the upgrade list (and will do so when pacman transitions from staging->core)
In case you end up with a non-functioning yay after the upgrade:
$ pacman -S --needed git base-devel
$ git clone https://aur.archlinux.org/yay.git
$ cd yay
$ makepkg -si
Pinned Comments
jguer commented on 2024-03-16 08:06 (UTC)
This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay
jguer commented on 2019-04-16 14:08 (UTC)
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.