@Linuxious remove your out-of-date mark - fakeroot is in the base-devel
group, which is a prerequisite for building AUR packages. Please familiarise yourself with the AUR building process.
Search Criteria
Package Details: yay 12.4.2-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: | 2325 |
Popularity: | 29.28 |
First Submitted: | 2016-10-05 17:20 (UTC) |
Last Updated: | 2024-09-19 14:27 (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)
- Show 26 more...
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 36 Next › Last »
morgenstern commented on 2020-10-25 20:16 (UTC)
sl13kp commented on 2020-10-24 13:09 (UTC)
This version has become very slow probably due to bugs
vitalijr2 commented on 2020-10-22 06:31 (UTC) (edited on 2020-10-22 06:31 (UTC) by vitalijr2)
What is happend with GPG keys?
spotify: gpg: keyserver receive failed: General error\n problem importing keys
caddy2: gpg: keyserver receive failed: General error\n problem importing keys
yochananmarqos commented on 2020-08-24 21:41 (UTC)
@duckdalbe: What are you talking about? Of course gcc
is in the base-devel
group.
duckdalbe commented on 2020-08-24 21:09 (UTC)
gcc
is a makedepends, should be added (and is not included in base-devel).
yochananmarqos commented on 2020-08-22 02:17 (UTC)
@darnir: -flto
is not used in the default /etc/makepkg.conf
, no changes are necessary except on your end, apparently.
whynothugo commented on 2020-08-21 22:17 (UTC)
@darnir See the pinned comment.
darnir commented on 2020-08-21 22:12 (UTC)
Just in case it helps anyone, the following diff fixed the build for me:
diff --git i/PKGBUILD w/PKGBUILD
index 8325d60..7a9e36b 100644
--- i/PKGBUILD
+++ w/PKGBUILD
@@ -20,8 +20,8 @@ sha256sums=('c0fb3df21a12d87c050317f68cc410b39d40f4af77192688956db67dc036a674')
build() {
export GOPATH="$srcdir"/gopath
export CGO_CPPFLAGS="${CPPFLAGS}"
- export CGO_CFLAGS="${CFLAGS}"
- export CGO_CXXFLAGS="${CXXFLAGS}"
+ export CGO_CFLAGS="$(echo "${CFLAGS}" | sed 's/-flto//g')"
+ export CGO_CXXFLAGS="$(echo "${CXXFLAGS}"| sed 's/-flto//g')"
export CGO_LDFLAGS="${LDFLAGS}"
cd "$srcdir/$pkgname-$pkgver"
darnir commented on 2020-08-21 22:07 (UTC)
I have been unable to build this package for a few months now. Everytime I try to build I end up with a log similar to: https://pastebin.com/A3KRz8vJ
On digging deeper, this seems to come from the fact that my makepkg.conf
contains `CFLAGS="... -flto ...". Apparently, turning on LTO in the C compiler, breaks the build.
If this is the case, the PKGBUILD should probably account for such scenarios
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.