The SDL forums have moved to discourse.libsdl.org.
This is just a read-only archive of the previous forums, to keep old links working.


SDL Forum Index
SDL
Simple Directmedia Layer Forums
SDL_mixer fails to configure with msys
Brian Kropf
Guest

Does anyone using SDL_mixer build with mingw/msys? It seems that the
last version of SDL_mixer built fine with mingw/msys, but now it fails
early during ./configure. If anyone has any guidance I'd appreciate it,
as I don't know much about autotools.

configure:2054: $? = 0
configure:2056: gcc -v </dev/null >&5
Reading specs from c:/dev/mingw/bin/../lib/gcc/mingw32/3.4.5/specs
Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld
--with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw
--enable-threads --disable-nls
--enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry
--disable-shared --enable-sjlj-exceptions --enable-libgcj
--disable-java-awt --without-x --enable-java-gc=boehm
--disable-libgcj-debug --enable-interpreter
--enable-hash-synchronization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.5 (mingw special)
configure:2059: $? = 0
configure:2061: gcc -V </dev/null >&5
gcc.exe: `-V' option must have argument
configure:2064: $? = 1
configure:2087: checking for C compiler default output file name
configure:2090: gcc c:\dev\VS_NET_2003\SDK\v1.1\include\
-D_GNU_SOURCE=1 -I/usr/local/include
c:\dev\VS_NET_2003\SDK\v1.1\include\ -D_GNU_SOURCE=1
-I/usr/local/include -L/usr/local/lib conftest.c >&5
c:\dev\mingw\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe:
c:\dev\VS_NET_2003\SDK\v1.1\include\: No such file: No such file or
directory
collect2: ld returned 1 exit status
configure:2093: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2132: error: C compiler cannot create executables
See `config.log' for more details.


thanks,
- brian kropf