From: ludo@gnu.org (Ludovic Courtès)
To: 19015@debbugs.gnu.org
Subject: bug#19015: SDL_mixer not linked against libmikmod
Date: Mon, 10 Nov 2014 23:16:48 +0100 [thread overview]
Message-ID: <87r3xak8fj.fsf@gnu.org> (raw)
Contrary to what’s intended, SDL_mixer ends up not linking against
libmikmod. Its ./configure run goes like this:
--8<---------------cut here---------------start------------->8---
checking for fork... yes
checking for vfork... yes
checking for libmikmod-config... /gnu/store/32mqj92g8bmq8bmr84sw2gckifld0ga0-libmikmod-3.3.3/bin/libmikmod-config
checking for libmikmod - version >= 3.1.10... configure: WARNING: *** Unable to find MikMod library (http://mikmod.raphnet.net/)
configure: WARNING: MOD support disabled
--8<---------------cut here---------------end--------------->8---
So it’s failing somewhere after the AC_PATH_PROG for libmikmod-config.
Ludo’.
next reply other threads:[~2014-11-10 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 22:16 Ludovic Courtès [this message]
2015-03-10 9:02 ` bug#19015: Fixed 宋文武
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3xak8fj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19015@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).