Arch Linux User Repository

edit: pinned. Comment on what to provide for help added.

What you guys experience is that your build environment is "tainted" by whatever packages exist on your system. I've had similar problems in the past with other packages :-(. With this particular package though, I can build it fine with and without chroot.

That's why pretty much all the distros build their packages in sane build environments.

As it's tough to figure out what plagues your systems, my recommendation stands - stick to chroot builds. I know it's a bother, but sadly that's the only help I can give you.

If it still doesn't work, please install devtools and provide a complete log of your build attempt with

extra-x86_64-build -c 2>&1 | tee build.log

Upload it to a pastebin service and post the link.

==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Starting build()...
flag provided but not defined: -i
usage: go build [-o output] [build flags] [packages]
Run 'go help build' for details.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: lazygit-git-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
lazygit-git - exit status 4

Changed go-pie to go in the PKGBUILD and everything went fine.

@fuero Can confirm it works here, Thanks a bunch.

@fuero happy to report it's working with yay on my box as well! Thanks for getting this resolved!

@neeks, dindybutts, Veras: Please try the latest version and report back - It works for me (tm) with yay.

Continuing from the Github issue thread...

I'm using yay like @dindybutts and I get the same errors. makepkg works as expected.

Since this is in the AUR and it's reasonable to expect people to build with AUR helpers, it be nice for this to get resolved some how.

However, I was successful in installing with pikaur, so these issues must lie in how certain AUR helpers are attempting to build.

The next course of action should be to open issues with yay and pacaur

I think the issue was something to do with my $GOPATH or $GOROOT not being set so I made a simple makefile where I set both paths and it compiles fine, It still has to invoke go get -d ./.. in the makefile though which I think is possibly unnecessary since go build should automagically get the dependencies(?) but this works for me.

Many thanks for the help @fuero

edit: pinned. Comment on what to provide for help added.

What you guys experience is that your build environment is "tainted" by whatever packages exist on your system. I've had similar problems in the past with other packages :-(. With this particular package though, I can build it fine with and without chroot.

That's why pretty much all the distros build their packages in sane build environments.

As it's tough to figure out what plagues your systems, my recommendation stands - stick to chroot builds. I know it's a bother, but sadly that's the only help I can give you.

If it still doesn't work, please install devtools and provide a complete log of your build attempt with

extra-x86_64-build -c 2>&1 | tee build.log

Upload it to a pastebin service and post the link.

@fuero

Here's the log you asked for: https://pastebin.com/MzTVaNyN

It's strange, it seems to build fine with the command you provided and with a simple makepgk -si but fails while using both my aur helpers, yay and pacaur

@dindybutts

the deps are all vendored by the author, so there's no need to download anything.

Please provide a complete log of your build attempt with

extra-x86_64-build -c 2>&1 | tee build.log

Upload it to a pastebin service and post the link.