Package Details: gzdoom 4.14.2-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: 168
Popularity: 0.59
First Submitted: 2009-02-22 22:28 (UTC)
Last Updated: 2025-05-05 15:13 (UTC)

Dependencies (27)

Sources (3)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 17 Next › Last »

ProfessorKaos64 commented on 2017-01-03 03:11 (UTC)

The regular fmodex will not work, as it only installs 4.44.58, not 4.44.62.

annoyingduck commented on 2017-01-02 16:33 (UTC)

I'm on Manjaro, I too got the fmodex dependency fail when attempting to update from previous release. The fix is simple: Install regular fmodex package from AUR, update Gzdoom, remove original fmodox4.26.36 package that previous release installed. Worked fine for me.

grubber commented on 2016-12-31 15:32 (UTC)

@GI_Jack, these are the correct dependencies. About the variables, please suggest a better way to a) deal with fmodex being incompatible between versions b) make parts of the build configurable.

GI_Jack commented on 2016-12-31 13:29 (UTC)

please fix the dependencies Proceed with installation? [Y/n] y error: package 'fmodex' was not found Edit gzdoom PKGBUILD with $EDITOR? [Y/n] y error: package 'fmodex' was not found error: package 'fmodex' was not found depends=('fluidsynth' ${_fmodex:+$(LC_ALL=C pacman -Q $_fmodex | sed -r 's/ /=/;s/-.*$//')} 'gtk2' 'libgl' 'libgme' ${_openal:+'libsndfile'} ${_openal:+'mpg123'} ${_openal} 'sdl2' ) What the fuck is that happy horse shit?, there is no need for variablized deps.

grubber commented on 2016-12-29 14:48 (UTC)

@Flisk, the segfault should be fixed now that the last fmodex version is used by default. @notuxius, works for me, try updating your fmodex package to 4.44.62.

Flisk commented on 2016-12-28 06:04 (UTC)

@grubber That's what I do already. I was wondering if other people were having problems with Fmod-enabled builds. If that were the case, it would make sense to disable it by default. Doesn't seem like anyone is having this problem (have you tried reproducing it?), and I'm not interested in pinpointing the exact cause when builds without Fmod work fine.

notuxius commented on 2016-12-27 18:35 (UTC) (edited on 2016-12-27 18:51 (UTC) by notuxius)

@grubber error on build: :: resolving dependencies... :: no results found for fmodex=4.44.62

grubber commented on 2016-12-14 17:20 (UTC)

Why by default? You can easily disable it yourself in the PKGBUILD.

Flisk commented on 2016-11-25 00:33 (UTC)

Are there any reasons not to disable fmodex by default? I'm currently getting segfaults when discovering secrets on fmodex-enabled builds, and the problem goes away when I build without fmod. Am I alone with that issue?

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 17 Next › Last »