Arch Linux User Repository

Hi, is it possible to add a GTK2 package or option? I noticed GTK3 does have a small impact on performance. GTK2 would only require the build line to be: 'arch-meson snes9x/gtk build -D gtk2=true -D gtk3=false -D wayland=false'

/snes9x-git/PKGBUILD: line 33: ./autogen.sh: No such file or directory
==> ERROR: A failure occurred in build().
Aborting...
Error making: snes9x-git (snes9x-gtk-git)

I checked "ls /snes9x-git/src/snes9x-git/gtk/"
AUTHORS data meson.build meson_options.txt po src

There is no ./autogen.sh file where PKGBUILD is calling it at "line 33"

cd ../gtk
./autogen.sh

Thanks YamashitaRen, will fix

Seems like snes9x-gtk depends on minizip :

snes9x-gtk: error while loading shared libraries: libminizip.so.1: cannot open shared object file: No such file or directory

@banzr this package must conflict with vanilla snes9x and snes9x-gtk, since they provide the same files. You noted "I get an error that snes9x conflicts with snes9x-git-gtk." That is not true. The conflicts is "snes9x, snes9x-gtk" not "snes9x, snes9x-git-gtk". The provides should not be "package-git", but always "package" when there is an existing package, AUR or not, that provides the same files. Since the base package builds both, I will adjust the conflicts so snes9x-gtk-git conflcits with snes9x-gtk, and snes9x-git conflicts with snes9x only. gtk should not conflict with non-gtk.

There's a simple error that I receive after successfully building the snes9x-git-gtk package. As soon as I attempt to install the snes9x package I get an error that snes9x conflicts with snes9x-git-gtk. Please remove these conflicts or change your snes9x-git package to provide snes9x-git. I prefer removing the conflicts unless there is some incompatibility with your gtk layer with the vanilla snes9x package. Removing the conflict allowed my package to build flawlessly. I didn't have the vanilla snes9x package previously installed before building your package.

Thanks, I was able to install without problems using the chroot method.

See the below. Seems a few touch commands will help this.

http://stackoverflow.com/questions/5731023/autotools-force-make-not-to-rebuild-configure-makefile

https://www.gnu.org/savannah-checkouts/gnu/automake/manual/html_node/CVS.html

It is difficult to reproduce this. Sometimes it manifests itself, other times, not. Keep in mind this is a dormant project and doesn't have much activity at all. I would suggest clearing you package cache if using a helper like pacaur (~/.cache/pacaur/snes9x-git).

The PKGBUILD produces two packages. As for the errors, I'll try soon, but I always test with makechrootpkg and a clean chroot, so it's unlikely that it's this build. I would suggest cloning the upstream repository and manually compiling things to check it isn't your system. Also, you could check the arch wiki for building in a clean chroot, which is also a good idea.