Warzone 2100 Forums

Posted: **07 Nov 2009, 20:19**

Hello, I'm trying to install warzone 2100 2.2.4 on my computer and its giving me the following troubling messages when I run make. I have all the dependencies including openal installed and the OPENAL_CFLAGS and OPENAL_LIBS environment variables set properly. Is there a config file I forgot to adjust or is there a bug? If it makes any difference I recently upgraded to the latest libtool 2.2.6 http://www.gnu.org/software/libtool/ to compile something else.

Code: Select all

/home/xovan/Downloads/warzone2100-2.2.4/lib/sequence/sequence.c:228: undefined reference to `alGenSources'                                                                  
/home/xovan/Downloads/warzone2100-2.2.4/lib/sequence/sequence.c:232: undefined reference to `alGenBuffers'                                                                  
/home/xovan/Downloads/warzone2100-2.2.4/lib/sequence/sequence.c:234: undefined reference to `alGenBuffers'

and it keeps talking about undefined references for a lenghty time and then ends with this

Code: Select all

collect2: ld returned 1 exit status
make[3]: *** [warzone2100] Error 1
make[3]: Leaving directory `/home/xovan/Downloads/warzone2100-2.2.4/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/xovan/Downloads/warzone2100-2.2.4/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/xovan/Downloads/warzone2100-2.2.4'
make: *** [all] Error 2

Posted: **07 Nov 2009, 20:57**

Is there a config file I forgot to adjust

The compiler is not seeing your openal libs. Did you run configure?

Note that all your libs will need to be 64 or 32 bit depending on how you are compiling.

Posted: **07 Nov 2009, 21:44**

stiv wrote: The compiler is not seeing your openal libs. Did you run configure?

Yeah.

stiv wrote: Note that all your libs will need to be 64 or 32 bit depending on how you are compiling.

I did a

export ARCH="x86_64"

to guarantee that it is properly compiling the binaries and stuff for 64 bit but openal still installed to /usr/local/lib/ instead of /usr/local/lib64/ do you think I need to recompile openal with some custom options?

Posted: **08 Nov 2009, 01:37**

SOLVED!

Here's the problem, openal needs to be explicitly compiled for x86_64 it doesn't automagically detect your ARCH so by modifying the openal Slackbuild to make the ARCH set to x86_64 and adjusting my OPENAL_CFLAGS and OPENAL_LIBS to reflect the new installation of openal I got warzone 2100 to play.

I really should've payed more attention to the Slackware way of manually doing things instead of being so lazy or I wouldn't have been in this mess to begin with.

Warzone 2100 Forums

[SOLVED]Cannot compile warzone 2100 on slackware 13

[SOLVED]Cannot compile warzone 2100 on slackware 13

Re: Cannot compile warzone 2100 2.2.4 x86_64 on slackware 13

Re: Cannot compile warzone 2100 2.2.4 x86_64 on slackware 13

Re: Cannot compile warzone 2100 2.2.4 x86_64 on slackware 13