From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] gzdoom: fatal error: only SDL 2.0.6 or later is supported
Date: Mon, 10 Oct 2022 04:56:25 +0200 [thread overview]
Message-ID: <20221010025625.YAmo5Zn3rKd41MZkVhXA0zV3PZsQhUX0-lqw8L2QjEc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39849@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
Closed issue by Vulldozer on void-packages repository
https://github.com/void-linux/void-packages/issues/39849
Description:
### Is this a new report?
Yes
### System Info
Void 5.19.13_1 x86_64 AuthenticAMD notuptodate rDDFFFFFFF
### Package(s) Affected
gzdoom-4.7.1_1, SDL2-2.24.0_1, SDL2-devel-2.24.0_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
gzdoom requires SDL2-2.0.6 or later to work, and it is packaged with a dependency for the latest SDL2 (2.24.0_1 at the time of writing this).
after installing gzdoom and making sure SDL2 is up to date, running the gzdoom command or launching it elsewhere should start the game.
### Actual behaviour
after running gzdoom and picking an any iwad file you get an error and it exits.
fatal error: only SDL 2.0.6 or later is supported.
gzdoom can't run the game with the latest version of SDL2, but after a downgrade to SDL2-2.0.22 using the xdowngrade tool the issue is fixed and the game works.
### Steps to reproduce
1. install gzdoom `xbps-install -Su gzdoom`
2. run `gzdoom`
3. pick any iwad file (if you don't have any, you can get the freedoom iwad a libre/free iwad).
4. see error.
prev parent reply other threads:[~2022-10-10 2:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 21:19 [ISSUE] " Vulldozer
2022-10-09 21:51 ` oreo639
2022-10-09 21:51 ` oreo639
2022-10-10 2:54 ` sgn
2022-10-10 2:56 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221010025625.YAmo5Zn3rKd41MZkVhXA0zV3PZsQhUX0-lqw8L2QjEc@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).