Issues building SDL_mixer with mingw / msys

SDL Development
1

Has anyone else been able to build SDL_mixer with Mingw / Msys? I’d
really like to be able to use SDL_mixer again, but whenever I try to run
configure it fails before completing with the following errors:

configure: creating ./config.status
config.status: creating Makefile
config.status: WARNING: Makefile.in seems to ignore the --datarootdir
setting
config.status: creating SDL_mixer.spec
config.status: creating SDL_mixer.qpg
config.status: executing default commands
/bin/sh: -c: line 1: unexpected EOF while looking for matching `"’
/bin/sh: -c: line 2: syntax error: unexpected end of file
make: *** [depend] Error 2

2

Has anyone else been able to build SDL_mixer with Mingw / Msys? I’d
really like to be able to use SDL_mixer again, but whenever I try to run
configure it fails before completing with the following errors:

[snipped]

I just tried to get a working msys configuration and I wasn’t able to.
I downloaded msys 1.0.10, gcc, and binutils and no matter what I passed
to gcc, I got “no input files”.

Do you have any steps I can use to set up that environment for testing?

Thanks!
-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment

3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian Kropf wrote:

Has anyone else been able to build SDL_mixer with Mingw / Msys? I’d
really like to be able to use SDL_mixer again, but whenever I try to run
configure it fails before completing with the following errors:

configure: creating ./config.status
config.status: creating Makefile
config.status: WARNING: Makefile.in seems to ignore the --datarootdir
setting
config.status: creating SDL_mixer.spec
config.status: creating SDL_mixer.qpg
config.status: executing default commands
/bin/sh: -c: line 1: unexpected EOF while looking for matching `"’
/bin/sh: -c: line 2: syntax error: unexpected end of file
make: *** [depend] Error 2

Hi, I ran into something like that when I was trying to build
SDL_mixer. I ran dos2unix on all the files to change the DOS end of
line to a unix style end of line. Not sure if this is what is causing
your error though, but it might be worth a try.

Another thing I found out was that the SDL packages all seemed to
treat the windows INCLUDE environment variable differently. I think
SDL_image (or it may have been mixer, I can’t recall now), for
example, could not handle the C:\ in the include path that I had set.
I had to set the variable to blank, then add my include paths (like
/usr/include) directly to the Makefile before running make. I also had
to do the same with my windows LIB environment variable.

Needless to say I had a hec of a time getting these to build using
Msys, but finally I did manage to get everything built and working.

Jim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGo7vQQuDJiZ/QrH0RAvwDAKDJvu8Iq/X5tJ+typJZV/N2zqbrEgCcDql5
jiHrUj8g6LaTG8JSxJlzEK0=
=eNQM
-----END PGP SIGNATURE-----

4

Do you have any steps I can use to set up that environment for testing?

My basic setup is as follows:

For Mingw download and extract archives to the same location (e.g.
c:\dev\mingw):
gcc-core-3.4.5-20060117-1.tar.gz
gcc-g+±3.4.5-20060117-1.tar.gz
mingw-runtime-3.12.tar.gz
w32api-3.9.tar.gz

For MSys download the following (run the pos-install for MSys and
provide the mingw mapping)
MSYS-1.0.10.exe
msysDTK-1.0.1.exe

There is a bunch of updated files in the snapshot and current sections,
but this is pretty much the minimum you’ll need to get the configure error.

thanks,

  • brian kropf
5

James Barrett wrote:

Another thing I found out was that the SDL packages all seemed to
treat the windows INCLUDE environment variable differently. I think
SDL_image (or it may have been mixer, I can’t recall now), for
example, could not handle the C:\ in the include path that I had set.
I had to set the variable to blank, then add my include paths (like
/usr/include) directly to the Makefile before running make. I also had
to do the same with my windows LIB environment variable.

Ahhh, that was it! I have Visual Studio installed, which sets an
environment variable for INCLUDE to point to the Visual Studio’s include
directory. I have been deleting the INCLUDE from the configure script,
but apparently the configure works fine if I just set the INCLUDE
environment variable to an empty string.

thanks for the tip!

  • brian kropf