AUR (en) - gzdoom-git

Git Clone URL:	https://aur.archlinux.org/gzdoom-git.git (read-only, click to copy)
Package Base:	gzdoom-git
Description:	Feature centric port for all Doom engine games (git version)
Upstream URL:	http://www.zdoom.org/
Licenses:	GPL3, BSD, LGPL3
Conflicts:	gzdoom
Provides:	gzdoom
Replaces:	gzdoom-legacy-git, gzdoom1-git
Submitter:	grubber
Maintainer:	grubber
Last Packager:	grubber
Votes:	23
Popularity:	0.94
First Submitted:	2013-06-25 15:27 (UTC)
Last Updated:	2023-09-27 07:36 (UTC)

Latest Comments

XAVeRY commented on 2023-09-28 09:40 (UTC)

The pkgver() in the current PKGBUILD returns 4.12pre+3+g40ec46e6e, but the pkgver variable is set to 4.12pre+3+g40ec46e6ea, which means that AUR helpers will keep notifying you about a possible update.

Please change to pkgver=4.12pre+3+g40ec46e6e in the PKGBUILD, thanks!

gustavo6046 commented on 2022-12-15 03:15 (UTC) (edited on 2022-12-15 03:34 (UTC) by gustavo6046)

GZDoom 4.10 seems to have introduced a PROGDIR argument/definition that basically obsoletes that section of the patch. It can be taken advantage of by passing -DPROGDIR="/usr/lib/gzdoom" in the pkgbuild's CXXFLAGS.

This, alongside stripping that particular diff section from the patch file, fixes the issue I and @CasualUser have encountered.

Here is a git diff from the, as of writing, current version of the AUR repo (6497acf64):

diff --git a/0001-Fix-file-paths.patch b/0001-Fix-file-paths.patch
index cc8adb6..00b7c23 100644
--- a/0001-Fix-file-paths.patch
+++ b/0001-Fix-file-paths.patch
@@ -8,31 +8,6 @@ Subject: [PATCH] Fix file paths
  src/gameconfigfile.cpp                   | 10 ++--------
  2 files changed, 3 insertions(+), 21 deletions(-)

-diff --git a/src/common/platform/posix/sdl/i_main.cpp b/src/common/platform/posix/sdl/i_main.cpp
-index a28b90f01..7299029fd 100644
---- a/src/common/platform/posix/sdl/i_main.cpp
-+++ b/src/common/platform/posix/sdl/i_main.cpp
-@@ -175,19 +175,7 @@ int main (int argc, char **argv)
-   Args = new FArgs(argc, argv);
- 
-   // Should we even be doing anything with progdir on Unix systems?
--  char program[PATH_MAX];
--  if (realpath (argv[0], program) == NULL)
--      strcpy (program, argv[0]);
--  char *slash = strrchr (program, '/');
--  if (slash != NULL)
--  {
--      *(slash + 1) = '\0';
--      progdir = program;
--  }
--  else
--  {
--      progdir = "./";
--  }
-+  progdir = "/usr/lib/gzdoom/";
- 
-   I_StartupJoysticks();
- 
 diff --git a/src/gameconfigfile.cpp b/src/gameconfigfile.cpp
 index 17898f3ae..7bfb63205 100644
 --- a/src/gameconfigfile.cpp
diff --git a/PKGBUILD b/PKGBUILD
index 6f6814a..c94da48 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Jan Cholasta <grubber at grubber cz>

 pkgname=gzdoom-git
-pkgver=4.10pre+16+gd422737a7
+pkgver=4.11pre+8+gde65d1b96
 pkgrel=1
 pkgdesc='Feature centric port for all Doom engine games (git version)'
 arch=('i686' 'x86_64' 'aarch64')
@@ -42,7 +42,7 @@ source=('gzdoom::git+https://github.com/coelckers/gzdoom.git'
         '0001-Fix-file-paths.patch')
 sha256sums=('SKIP'
             '59122e670f72aa2531aff370e7aaab2d886a7642e79e91f27a533d3b4cad4f6d'
-            '195a9d1ec0489bd38f1d6c40763e66773dd74f5f719acb6afa32a077fdb0b8f4')
+            '80269a3cc5b2a3a8c3070e9ec267ec17f68f7cb884b1dee657b4d6178784abbb')

 pkgver() {
     cd gzdoom
@@ -59,10 +59,11 @@ build() {
     mkdir -p build
     cmake -B build \
           -D CMAKE_BUILD_TYPE=Release \
-          -D CMAKE_CXX_FLAGS="${CXXFLAGS} -ffile-prefix-map=\"$PWD\"=. -DSHARE_DIR=\\\"/usr/share/gzdoom\\\"" \
+          -D CMAKE_CXX_FLAGS="${CXXFLAGS} -ffile-prefix-map=\"$PWD\"=. -DSHARE_DIR=\\\"/usr/share/gzdoom\\\" -D PROGDIR=\\\"/usr/lib/gzdoom\\\"" \
           -D INSTALL_RPATH=/usr/lib \
           -D DYN_GTK=OFF \
-          -D DYN_OPENAL=OFF
+          -D DYN_OPENAL=OFF \
+          -Wno-dev
     make -C build
 }

CasualUser commented on 2022-11-22 11:59 (UTC) (edited on 2022-11-22 12:00 (UTC) by CasualUser)

patching file src/common/platform/posix/sdl/i_main.cpp

Hunk #1 FAILED at 175.

1 out of 1 hunk FAILED -- saving rejects to file src/common/platform/posix/sdl/i_main.cpp.rej

patching file src/gameconfigfile.cpp

Hunk #1 succeeded at 121 (offset 2 lines).

Hunk #2 succeeded at 141 (offset 2 lines).

Hunk #3 succeeded at 168 (offset 2 lines).

The patch needs and update.

nikdog commented on 2022-06-23 23:26 (UTC)

==> Making package: gzdoom-git 4.8pre+493+g989dcfcf1-1 (Thu 23 Jun 2022 14:03:02 PDT)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> zmusic>=1.1.8
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: gzdoom-git

Using zmusic-git to fill the zmusic dependency doesn't work. I don't know if this is a misconfiguration of the zmusic-git PKGBUILD or the gzdoom-git PKGBUILD. I tried to find a way to list OR dependencies in depends=(), but couldn't. As a temp workaround I just changed zmusic to zmusic-git in the PKGBUILD for gzdoom.

jwhickman commented on 2022-03-08 04:00 (UTC) (edited on 2022-09-20 18:34 (UTC) by jwhickman)

[UPDATE: I had forgotten that I added '-flto' as a makepkg.conf build flag long ago; removing it fixes this] Fyi, I'm getting a build failure for this:

./src/common/objects/autosegs.cpp:72:1: error: ‘ActionFunctonsDummyPointer’ causes a section type conflict with ‘_PlayerInfo_GetDisplayColor_HookPtr’
./src/d_netinfo.cpp:221:1: note: ‘_PlayerInfo_GetDisplayColor_HookPtr’ was declared here
./src/common/objects/autosegs.cpp:74:1: error: ‘ClassFieldsDummyPointer’ causes a section type conflict with ‘VMField_DBot_dest_HookPtr’
./src/playsim/bots/b_bot.cpp:66:1: note: ‘VMField_DBot_dest_HookPtr’ was declared here

CasualUser commented on 2022-01-12 08:05 (UTC) (edited on 2022-01-12 08:51 (UTC) by CasualUser)

Nope, i didn't mess with git. I've modified the script with pamac on manjaro replacing the line 'gzdoom::git://github.com/coelckers/gzdoom.git' with 'gzdoom::git+https://github.com/coelckers/gzdoom' and it builds. The raze-git script has the https as well. Can this repository be updated this way? Thanks.

Edit : it builds again, but :

No more unauthenticated Git

On the Git protocol side, unencrypted git:// offers no integrity or authentication, making it subject to tampering. We expect very few people are still using this protocol, especially given that you can’t push (it’s read-only on GitHub). We’ll be disabling support for this protocol.

architector4 commented on 2022-01-12 03:29 (UTC) (edited on 2022-01-12 03:33 (UTC) by architector4)

The unauthenticated git protocol on port 9418 is no longer supported.

This seems to be a problem on your end - in my case everything still works. You might have messed with git settings before in a way that github does not accept? See if you can change your configuration there.

Also check the github link - it has a timeline table showing that on 11th January 2022 the "final brownout" was scheduled, where more insecure protocols are set to be unsupported, aswell as unencrypted git protocol. That seems to be what hit you this time in particular!

CasualUser commented on 2022-01-11 20:16 (UTC) (edited on 2022-01-11 20:16 (UTC) by CasualUser)

Unable to build again.

Unable to update git repository :

The unauthenticated git protocol on port 9418 is no longer supported.

Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.

CasualUser commented on 2022-01-06 10:14 (UTC)

Problem fixed. Thanks.

FabioLolix commented on 2022-01-04 00:16 (UTC)

There aren't git submodules so 'git submodule update --init' can be removed, also git submodules sources need to be downloaded in source=()

1 2 3 4 5 Next › Last »

Arch Linux User Repository

Search Criteria

Package Details: gzdoom-git 4.12pre+3+g40ec46e6ea-1

Package Actions

Dependencies (28)

Required by (11)

Sources (3)