Package Details: chocolate-doom 3.1.1-1

Git Clone URL: https://aur.archlinux.org/chocolate-doom.git (read-only, click to copy)
Package Base: chocolate-doom
Description: Historically-accurate Doom, Heretic, Hexen, and Strife ports.
Upstream URL: http://www.chocolate-doom.org/
Licenses: GPL2
Conflicts: chocolate-common, chocolate-heretic, chocolate-hexen, chocolate-strife
Replaces: chocolate-common, chocolate-heretic, chocolate-hexen, chocolate-strife
Submitter: None
Maintainer: Technochips
Last Packager: Technochips
Votes: 63
Popularity: 0.008787
First Submitted: 2006-07-30 06:27 (UTC)
Last Updated: 2026-01-14 13:01 (UTC)

Dependencies (8)

Required by (2)

Sources (1)

Latest Comments

1 2 3 Next › Last »

Technochips commented on 2026-01-14 13:10 (UTC)

Hiya, I updated the package. ceidways's patch was implemented. Should be working good for now.

ceidways commented on 2025-12-19 02:31 (UTC) (edited on 2025-12-19 02:31 (UTC) by ceidways)

GCC issue fixed upstream as of ver 3.1.1

I updated the PKGBUILD and removed the patch 0001-man-docgen-Use-raw-string-literals-for-regular-expre.patch which was implemented upstream.

Tested and working on Arch Linux x86_64 (2025-12-19) GCC 15.2.1

Patch here: https://gist.github.com/ceidways/44c907c20621fd601a25eaa61889d1c8

(First time doing anything for AUR. Did my best research but please tell me if I missed anything)

AeriaVelocity commented on 2025-10-01 18:34 (UTC)

Marked out-of-date due to no update in around two months since the GCC issue was reported

josephlat commented on 2025-08-24 18:44 (UTC)

Alternatively, here is a patch you can apply to the source itself:

diff -ura chocolate-doom-chocolate-doom-3.1.0.orig/src/doomtype.h chocolate-doom-chocolate-doom-3.1.0.new/src/doomtype.h
--- chocolate-doom-chocolate-doom-3.1.0.orig/src/doomtype.h 2024-07-31 17:33:46.000000000 -0400
+++ chocolate-doom-chocolate-doom-3.1.0.new/src/doomtype.h  2025-08-24 14:31:34.551040413 -0400
@@ -100,9 +100,9 @@

 #include <inttypes.h>

-#if defined(__cplusplus) || defined(__bool_true_false_are_defined)
+#if defined(__cplusplus) || __STDC_VERSION__==202311L || defined(__bool_true_false_are_defined)

-// Use builtin bool type with C++.
+// Use builtin bool type with C++ and C23.

 typedef bool boolean;


josephlat commented on 2025-08-24 04:09 (UTC) (edited on 2025-08-24 04:11 (UTC) by josephlat)

After doing some fiddling, it seems the issue is due to C23 making true and false into keywords, with choclate doom defining true and false itself as an enum. An easy fix to get it working is to force it to compile as C17 instead.

diff of PKGBUILD:

43c43
<   ./configure --prefix=/usr
---
>   CFLAGS='--std=c17' ./configure --prefix=/usr

Bombyyy commented on 2025-06-09 00:29 (UTC)

get same errors as Jvazrk below

https://pastebin.com/UJLfgDKL

Jzavrk commented on 2025-06-04 22:00 (UTC)

chocolate-doom won't compile with gcc last version

make[3]: Entering directory '/home/jiji/.cache/yay/chocolate-doom/src/chocolate-doom-chocolate-doom-3.1.0/src/doom'
  CC       am_map.o
In file included from ../../src/deh_main.h:21,
                 from am_map.c:22:
../../src/doomtype.h:113:5: error: cannot use keyword ‘false’ as enumeration constant
  113 |     false,
      |     ^~~~~
../../src/doomtype.h:113:5: note: ‘false’ is a keyword with ‘-std=c23’ onwards
make[3]: *** [Makefile:541: am_map.o] Error 1

jsx commented on 2022-11-10 11:47 (UTC)

Hmm, is this project still alive? Anybody who can help out configuring the background music? I set up some arch linux machines and on none the music is working out of the box, although it installs timidity as a dependency.

jsx commented on 2022-11-01 20:55 (UTC)

Thanks for providing this great application. Since a while I don't have any background sound and get the message "Error loading midi: Couldn't open timidity.cfg". When setting timidity_cfg_path in the config file to a valid timidity.cfg, it says "Error loading midi: Couldn't open /tmp/timidity.cfg" although I set the path to something else than /tmp/timidity.cfg (but problem persists when setting it to /tmp/timidity.cfg, too). So far I think it's my fault and like to ask for help here. When copying a valid timidity.cfg to /tmp/timidity.cfg, chocolate doom will delete it and display "Error loading midi: Couldn't open /tmp/timidity.cfg", at least for this I'm sure it's a bug.