Package Details: kitty-git 1:0.32.2.r373.ge9c4e7310-2

Git Clone URL: https://aur.archlinux.org/kitty-git.git (read-only, click to copy)
Package Base: kitty-git
Description: Modern, hackable, featureful, OpenGL based terminal emulator
Upstream URL: https://sw.kovidgoyal.net/kitty/
Licenses: GPL3
Conflicts: kitty
Provides: kitty
Submitter: mkindshofer
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 25
Popularity: 0.003142
First Submitted: 2017-01-10 15:54 (UTC)
Last Updated: 2024-03-02 09:16 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

iano200 commented on 2024-03-16 15:34 (UTC)

Looks like the developer of kitty has added in custom build flags for gcc or clang so the setup.py is adding in the flags that he has added in plus the flags that are specified in the CFLAGS var located in /etc/makepkg.conf together resulting in specifically an error by gcc in my case, complaining that _FORTIFY_SOURCE has been redefined. He has specified -D_FORTIFY_SOURCE=2 and the value flag in /etc/makepkg.conf is set to -D_FORTIFY_SOURCE=3 which causes the build to fail with a not very helpful error message.

@FabioLolix to get around this add:

options=(!buildflags)

Into the PKGBUILD file and it should be able to build properly again, I have ran it multiple times with that set.

zomgugoff commented on 2024-03-15 22:39 (UTC)

Thanks for the assistance. It would be nice to know what the issue is with the OS detection.

FabioLolix commented on 2024-03-15 22:33 (UTC)

although it threw some errors right at the end:

==> Running checkpkg
error: target not found: kitty-git
error: target not found: kitty-terminfo-git
error: target not found: kitty-shell-integration-git

that's because they aren't already in a repository

zomgugoff commented on 2024-03-15 22:32 (UTC) (edited on 2024-03-15 22:32 (UTC) by zomgugoff)

Base-devel was already installed. I had installed a prior build of kitty-git not too long ago (1:0.32.2.r407.gd33afd4e9-1) without issue.

extra-x86_64-build appeared to build, although it threw some errors right at the end:

==> Running checkpkg
error: target not found: kitty-git
error: target not found: kitty-terminfo-git
error: target not found: kitty-shell-integration-git

FabioLolix commented on 2024-03-15 21:55 (UTC)

@zomgugoff can't reproduce

zomgugoff commented on 2024-03-15 21:48 (UTC) (edited on 2024-03-15 21:50 (UTC) by zomgugoff)

I'm on Arch x86_64.

Linux ERIK 6.7.9-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 08 Mar 2024 01:58:50 +0000 x86_64 GNU/Linux

I'm currently installing via Yay. I have not tried manually via pkgbuild.

FabioLolix commented on 2024-03-15 21:43 (UTC)

@zomgugoff On what OS and architecture are you? What command have you used?

zomgugoff commented on 2024-03-15 21:42 (UTC) (edited on 2024-03-15 21:47 (UTC) by zomgugoff)

Getting an error about target architecture today:

==> Starting pkgver()...
==> Starting build()...
Failed to determine target architecture compiling test program failed with exit code: 1
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: kitty-git-exit status 4

bbgun7 commented on 2024-03-13 13:24 (UTC) (edited on 2024-03-13 13:24 (UTC) by bbgun7)

I see, I didn't think about sharing the diff, but it should be pretty easy to generate locally.

I wasn't sure if version was necessary or not, that was just from the build instructions on kittys site.

The AUR "Add Comment" tips blurb ("Git commit identifiers referencing commits in the AUR package repository and URLs are converted to links automatically. Markdown syntax is partially supported.") links to https://daringfireball.net/projects/markdown/syntax for syntax, and that uses the <code> tag. I didn't realize backticks would even work. Might make sense to find a different guide and update the link.

FabioLolix commented on 2024-03-13 06:23 (UTC)

I've build kitty-git yesterday (kitty-git-1:0.33.0.r0.g04f8cb6d3-1-x86_64.pkg.tar.zst) with devtools and builded fine

I think this might be right?

The whole list without the diff isn't very useful

'python>=3.8' 'harfbuzz>=2.2.0' 'go>=1.22'

I'm not going to specify version, you need to have the system updated before building AUR packages

btw please don't <code> but backticks