Game Development Community

OpenAL problems on SuSE 9.1

by Martin Schultz · in Torque Game Engine · 06/29/2004 (12:18 pm) · 7 replies

Hi there,

I recently switched to Linux and am trying now to get torque running. After following the torque linux guide I get the following error when compiling (I did the "make -f mk/configure.mk OS=LINUX COMPILER=GCC3 BUILD=DEBUG" before):

Creating library out.GCC3.DEBUG/ljpeg_DEBUG.a
--> Compiling lungif/dgif_lib.c
--> Compiling lungif/egif_lib.c
--> Compiling lungif/gif_err.c
--> Compiling lungif/gifalloc.c
Creating library out.GCC3.DEBUG/lungif_DEBUG.a
--> Compiling audio/audio.cc
In file included from platform/platformAudio.h:14,
                 from audio/audio.h:10,
                 from audio/audio.cc:6:
platform/platformAL.h:13:24: al/altypes.h: File or Directory not found
platform/platformAL.h:14:25: al/alctypes.h: File or Directory not found
platform/platformAL.h:15:25: al/eaxtypes.h: File or Directory not found
platform/platformAL.h:19:24: al/al_func.h: File or Directory not found
platform/platformAL.h:20:25: al/alc_func.h: File or Directory not found
platform/platformAL.h:21:25: al/eax_func.h: File or Directory not found
In file included from audio/audio.h:10,
                 from audio/audio.cc:6:
platform/platformAudio.h:87: error: type specifier omitted for parameter '
   ALenum'
platform/platformAudio.h:87: error: syntax error before ',' token
platform/platformAudio.h:88: error: type specifier omitted for parameter '
   ALenum'
platform/platformAudio.h:88: error: syntax error before ',' token
platform/platformAudio.h:89: error: type specifier omitted for parameter '
   ALenum'


I'm using SuSE 9.1 Pro with the latest online patches. Both OpenAL libraries are installed (openAL + devel).

In the 9.0 version of SuSE I used before it worked like a charme.

Can anyone help out on this? Any help is greatly appreciated. Thanks :-)

Martin
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner Martin Schultz
#1
06/29/2004 (12:21 pm)
Forgot to mention that I surely saw that there are some file not found's, but I looked in the engine/platform directory and there were not those files. I'm using a 1.2.0 release of torque.

Torque Owner Eric Jergensen
#2
07/01/2004 (8:31 am)
Do a "locate altypes.h" and see if you do have them. If so, you will need to add a -I for it in CFLAGS. I may not have looked through the make files enought, but it looks like it would go in mk/conf.UNIX.mk.

Torque Owner Martin Schultz
#3
07/02/2004 (1:53 pm)
Hi,

I found the "altypes.h" here:

linux:/ # find . -name "altypes.h"
./usr/local/src/openal/include/AL/altypes.h
./usr/include/AL/altypes.h
./home/martin/torque/lib/openal/OpenBSD/al/altypes.h
./home/martin/torque/lib/openal/linux/al/altypes.h
./home/martin/torque/lib/openal/win32/al/altypes.h
./home/martin/torque/lib/openal/macCarb/al/altypes.h
./home/martin/torque/lib/openal/x86unix/al/altypes.h
./home/martin/torque/lib/openal/FreeBSD/al/altypes.h
...

and then I took a look in the file "mk/conf.UNIX.mk" and found this block here:

CFLAGS.GENERAL    = -DUSE_FILE_REDIRECT -I/usr/X11R6/include/ -MD -march=i586 \
		    -mcpu=i686 -ffast-math -pipe 
		    #-w -fno-exceptions -fno-check-new 
CFLAGS.RELEASE    = -O2 -finline-functions -fomit-frame-pointer 
CFLAGS.DEBUG      = -g -DTORQUE_DEBUG # -DTORQUE_DISABLE_MEMORY_MANAGER
CFLAGS.DEBUGFAST  = -O -g -finline-functions

and where exactly should I add now the "a -l" thing you mentioned?

Thanks for any help :-)

Martin

Torque Owner Martin Schultz
#4
07/02/2004 (2:10 pm)
I tried adding a "-I" at the end of the line CFLAGS.RELEASE and also tried at the end of the line CFLAGS.DEBUG, but it didn't help.

Torque Owner Martin Schultz
#5
07/03/2004 (5:43 am)
I found it. It was a somehow corrupt version of my source which made the errors. I downloaded a fresh 1_2_2 and it compiled fine (beside the usual warnings). So I think I somehow cracked my source. I'll fix that now :-)

Thanks everyone for the help!

Martin

Torque Owner Eric Jergensen
#6
07/03/2004 (8:33 pm)
In CFLAGS.GENERAL. But, looking at your error, I'd guess that you had a case conversion where AL got turned into al in your source. Glad you got it working.

Torque Owner Martin Schultz
#7
07/04/2004 (1:50 am)
Yepp, somehow the code messed up. Don't know why. But now it works like a charme :-)

Best,
Martin