AUR (en) - zdoom

Search Criteria

Package Details: zdoom 2.8.1-5

Git Clone URL:	https://aur.archlinux.org/zdoom.git (read-only)
Package Base:	zdoom
Description:	Advanced Doom source port
Upstream URL:	http://www.zdoom.org/
Licenses:	BSD, LGPL, custom:dumb, custom:BUILD, custom:doom
Submitter:	nvllsvm
Maintainer:	grubber
Last Packager:	grubber
Votes:	44
Popularity:	0.510814
First Submitted:	2008-04-15 22:44
Last Updated:	2017-05-09 08:03

Git Clone URL:

https://aur.archlinux.org/zdoom.git (read-only)

Package Base:

zdoom

Description:

Advanced Doom source port

Upstream URL:

http://www.zdoom.org/

Licenses:

Submitter:

nvllsvm

Maintainer:

grubber

Last Packager:

grubber

Votes:

Popularity:

0.510814

First Submitted:

2008-04-15 22:44

Last Updated:

2017-05-09 08:03

Latest Comments

Vaporeon commented on 2017-03-04 04:03

RIP ZDoom

grubber commented on 2016-12-30 18:12

@mrkline, install fmodex first (doesn't matter which version), then run makepkg to build zdoom.

mrkline commented on 2016-12-30 07:28

With makepkg -s:
==> Starting build()...
error: package 'fmodex' was not found
==> ERROR: A failure occurred in build().
Aborting...

With pacaur -S zdoom:
no results found for fmodex=4.44.62

I see an fmodex package in the AUR, but its current version is 4.44.58-1 and it's marked out of date. This package seems to request 4.44.62. Previously, the package was using fmodex4.26.36. What's the solution here?

grubber commented on 2016-12-29 14:45

@mrkline, @apollo11w, fixed.

apollo11w commented on 2016-12-28 01:28

-> Found launcher.desktop
-> Found 0001-Improve-Mac-GCC-errors-fix-to-work-only-for-GCC.patch
==> Validating source files with sha256sums...
zdoom-2.8.1-src.7z ... Passed
launcher.desktop ... Passed
0001-Improve-Mac-GCC-errors-fix-to-work-only-for-GCC.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build zdoom.
==> Restart building zdoom ? [y/N]

mrkline commented on 2016-12-16 17:15

Could the PKGBUILD be modified to set CC and CXX to gcc and g++, respectively? The build seems to use some GCC-specific flags (such as `-Wno-unused-but-set-variable`) and spits out a bunch of warnings if the user (such as myself) has CC and CXX set to clang and clang++.

Alternatively, we could patch the CMake config. This seems to be the culprit:

if(NOT CMAKE_CXX_COMPILER_ID STREQUAL "GNU" OR CMAKE_CXX_COMPILER_VERSION VERSION_GREATER "4.5")
set( CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-unused-but-set-variable" )

Is the "NOT" in that conditional a bug?

grubber commented on 2016-05-19 17:32

Huh, I could swear it worked fine for me. Will fix.

kimspindel commented on 2016-05-15 15:21

@punkrockguy318 I got the same error but managed to fix it by installing 'fmodex4.26.36' separately first

punkrockguy318 commented on 2016-05-13 02:34

FYI - Can't build on 64bit atm
:: Package(s) zdoom not found in repositories, trying AUR...
:: resolving dependencies...
:: no results found for fmodex=4.26.36

cronos commented on 2016-04-09 15:03

@grubber: ZDoom wanting to compile, the dependency fmodex can not find. URL not found fmodex 4.26.36 Package, the git repository is down.

Arch Linux User Repository