Works on Arm64 (Raspberry pi 4)
Just edited the pkgbuild file and added aarch64
to the arch and to fix the compiling issue with pygtk I added --build=unknown-unknown-linux
to the end of ./configure to make it work.
Git Clone URL: | https://aur.archlinux.org/pygtk.git (read-only, click to copy) |
---|---|
Package Base: | pygtk |
Description: | Python bindings for the GTK widget set |
Upstream URL: | https://wiki.gnome.org/Projects/PyGTK |
Keywords: | GTK Python widget |
Licenses: | LGPL-2.1-or-later |
Submitter: | arojas |
Maintainer: | creyon |
Last Packager: | creyon |
Votes: | 78 |
Popularity: | 0.22 |
First Submitted: | 2020-03-29 19:09 (UTC) |
Last Updated: | 2024-06-02 15:27 (UTC) |
Works on Arm64 (Raspberry pi 4)
Just edited the pkgbuild file and added aarch64
to the arch and to fix the compiling issue with pygtk I added --build=unknown-unknown-linux
to the end of ./configure to make it work.
I was able to compile on a raspberry pi 4 using http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD and modifying the pkgbuild to allow ARM architecture.
If anyone has an ARM device and is willing to help me test this on it, let me know so I can provide support for ARM architecture as well.
This was already discussed around https://aur.archlinux.org/packages/pygtk/?PP=250#comment-740369
The ONLY correct solution for updating config.guess is re-running autoreconf -fi
. However, the arch=('x86_64')
in the PKGBUILD does suggest it isn't tested on ARM, and it may or may not work or need additional workarounds to compile on such architectures. It is up to the maintainer to decide whether to add/test this support.
This package causes problems compiling on archlinux arm aarch64, because the config.guess in the sourcecode is way out of date. This can be worked around by including a file called 'config.guess' with this http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD content and copying it to the builddir. I did this by adding 'config.guess' to source, 'Skip' to sha256sums and 'cp ../config.guess ./' at the end of prepare in the PKGBUILD.
@zman0900 I think the point is that it is unlikely that someone maliciously replaces the patches but does not modify the PKGBUILD since they are downloaded as a bundle. Silent corruption should be caught when you clone the git repository, but is probably technically a possibility. Ideally the patches and the PKGBUILD would be signed, but in practice, the Arch way is buyer beware. You should be reading the PKGBUILD and associated files and make sure you know what they are doing.
How so? Without them, file integrity is not checked. Patches could be silently corrupted or maliciously replaced and it would go unnoticed.
@zman0900 because they are redundant.
Why are checksums skipped on the patch files?
What's the actual command you ran?
Pinned Comments
ragouel commented on 2022-06-11 23:26 (UTC) (edited on 2022-06-12 19:54 (UTC) by ragouel)
From official GNOME docs:
"Attention: PyGTK 2.24 will be the last release in the PyGTK series and will support the full GTK-2-24 API. PyGTK should not be used for new projects and existing PyGTK applications are recommended to be ported to PyGObject. See here for more information."
https://wiki.gnome.org/Projects/PyGTK/WhatsNew224
Please stop asking me to update this package. I only "keep" it, so that it is not messed with by others, as some older applications still rely on it to function.
Thank you.