Package Details: gzdoom 4.14.0-1

Git Clone URL: https://aur.archlinux.org/gzdoom.git (read-only, click to copy)
Package Base: gzdoom
Description: Feature centric port for all Doom engine games
Upstream URL: http://www.zdoom.org/
Licenses: GPL3, BSD, LGPL3
Replaces: gzdoom-legacy, gzdoom1
Submitter: None
Maintainer: xente
Last Packager: xente
Votes: 164
Popularity: 1.80
First Submitted: 2009-02-22 22:28 (UTC)
Last Updated: 2024-12-18 19:14 (UTC)

Dependencies (27)

Sources (4)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 17 Next › Last »

Tony556 commented on 2019-08-03 23:05 (UTC) (edited on 2019-08-04 05:45 (UTC) by Tony556)

[ 39%] Building CXX object src/CMakeFiles/zdoom.dir/posix/unix/gtk_dialogs.cpp.o
/home/tony/.cache/yay/gzdoom/src/gzdoom/src/posix/unix/gtk_dialogs.cpp:42:10: fatal error: gtk/gtk.h: No such file or directory
   42 | #include <gtk/gtk.h>
      |          ^~~~~~~~~~~
compilation terminated.

I reinstalled GTK2 and 3, and it even finds it when doing the first checks

-- Checking for module 'gtk+-3.0'
--   Found gtk+-3.0, version 3.24.10

EDIT:

Issue was that egl was missing, and having mesa-aco-git messed with that. Switching to base mesa fixed it.

doktorseven commented on 2019-02-25 14:26 (UTC) (edited on 2019-02-25 14:26 (UTC) by doktorseven)

Recent update to fluidsynth2 breaks fluidsynth for gzdoom.

Quick glance through source suggests src/sound/mididevices/music_fluidsynth_mididevice.cpp needs

#define FLUIDSYNTHLIB1 "libfluidsynth.so.1"

changed to

#define FLUIDSYNTHLIB1 "libfluidsynth.so.2"

but I haven't tested.

(my temp fix is creating symlink /usr/lib/libfluidsynth.so.1 to /usr/lib/libfluidsynth.so.2)

Trist commented on 2019-02-18 01:53 (UTC) (edited on 2019-03-18 00:19 (UTC) by Trist)

EDIT; keeping this post here even though its stupid. I don't know exactly whats wrong, I am behind a restricted network but github itself isn't blocked and I can download archives from the site itself, yet on several occasions I get this same error (minetest-get, fsearch, etc). Its clearly isolated to my machine, maybe something about the ".git" flips a filter. Whatever, its not the packages fault

Error on build;

fatal: unable to connect to github.com: github.com[0: 192.30.253.113]: errno=No route to host github.com[1: 192.30.253.112]: errno=No route to host

==> ERROR: Failure while downloading gzdoom git repo Aborting...

The PKGBUILD doesn't look wrong but I tried replacing the source line with an absolute git link and removing #tag=g${pkgver} anyways, neither worked. This problem has persisted for two weeks thus far and I can download the source from the git itself so I really don't get it. Any ideas, other than to compile it manually (which im finally gunna do because im itching for doom)?

Ulukai commented on 2019-01-02 23:00 (UTC)

Build 3.7.1-2 fixes all crash issues, thanks for the quick edit!

przemko27 commented on 2019-01-02 15:02 (UTC)

In regards to the problem reported below, I shall leave this compilation guide here for those that might want it. https://zdoom.org/wiki/Compile_GZDoom_on_Linux

Ulukai commented on 2019-01-02 13:54 (UTC)

There is a problem since version 3.7.0 and 3.7.1 with the use of asmjit. It makes GZDoom crash on some occasions, see this bug report from me on the GZDoom forums. https://forum.zdoom.org/viewtopic.php?f=2&t=63110 I believe the PKGBUILD needs to be updated to use GZDooms own asmjit instance instead. Can you have a look? Thanks!

Brottweiler commented on 2018-08-14 14:34 (UTC) (edited on 2018-08-14 14:34 (UTC) by Brottweiler)

==> WARNING: Package contains reference to $srcdir

usr/bin/gzdoom

SteelT commented on 2018-03-27 21:48 (UTC)

There's something weird when gzdoom is compiled from AUR, P2P networking mode don't work for 3+ players, it just gets stuck on "waiting for number" with number being a random player number each time, and the client/server mode just ends up being out of sync, none of these problems are present if I download the source code from site and compile manually.

grubber commented on 2018-02-25 06:05 (UTC)

Added the fix from upstream.