From: chloris-pale-green <chloris-pale-green@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: devilutionX: update to 1.4.1.
Date: Sat, 10 Sep 2022 14:25:38 +0200 [thread overview]
Message-ID: <20220910122538.6qJqt-68xKfhupv9iphNh515lTs2rzH51ZQovkGgar8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39184@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
New comment by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/pull/39184#issuecomment-1242718047
Comment:
> Seems there's a problem with building SDL_audiolib from the fetched source, we could try packaging it ourselves
>
> ...or not, it's not versioned in any way :/
It really does not seem to be versioned ... it's a bit like someone made a quick solution to their problem. I've also noticed that there is some overlap between contributors of devilutionX and SDL_audiolib. It's a good question if the package would be useful for anything else besides devilutionX.
However, I don't think it is a SDL_audiolib-specific issue that we're facing here. It seems to me that it simply doesn't find SDL libraries. They are detected as dynamic system libraries, but not found when things should get compiled.
next prev parent reply other threads:[~2022-09-10 12:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 13:47 [PR PATCH] " chloris-pale-green
2022-09-09 13:50 ` [PR PATCH] [Updated] " chloris-pale-green
2022-09-09 14:04 ` chloris-pale-green
2022-09-10 6:10 ` tranzystorek-io
2022-09-10 6:12 ` tranzystorek-io
2022-09-10 12:25 ` chloris-pale-green [this message]
2022-12-10 1:58 ` github-actions
2022-12-22 15:44 ` bugcrazy
2022-12-23 2:29 ` bugcrazy
2023-01-11 18:45 ` kruceter
2023-01-12 7:49 ` chloris-pale-green
2023-01-12 7:49 ` [PR PATCH] [Closed]: " chloris-pale-green
2023-01-15 1:39 [PR PATCH] " kruceter
2023-01-15 16:01 ` Vaelatern
2023-01-15 16:14 ` kruceter
2023-01-15 16:32 ` Vaelatern
2023-01-15 18:08 ` kruceter
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=20220910122538.6qJqt-68xKfhupv9iphNh515lTs2rzH51ZQovkGgar8@z \
--to=chloris-pale-green@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).