Slackware install...

[Chimaera]

anybody could install this on the slackware 9.0...

[Chimaera]

i run ./setup.sh:

root@darkstar:~/vegastrike-0.4.1-installer#./setup.sh
...
checking for GLU library... no
checking for GLU library (with pthreads)... no
checking for MesaGLU library... no
checking for MesaGLU library (with pthreads)... no
checking for openglu32 library... no
checking for openglu32 library (with pthreads)... no
*** Hmm, you don't seem to have OpenGLU libraries installed in the standard
*** location (/usr/lib). I'll check in /usr/X11R6/lib, since
*** many distributions (incorrectly) put OpenGLU libs there.
...
checking GL/glext.h usability... no
checking GL/glext.h presence... yes
configure: WARNING: GL/glext.h: present but cannot be compiled
configure: WARNING: GL/glext.h: check for missing prerequisite headers?
configure: WARNING: GL/glext.h: proceeding with the preprocessor's result
configure: WARNING: ## ------------------------------------ ##
configure: WARNING: ## Report this to bug-autoconf@gnu.org. ##
configure: WARNING: ## ------------------------------------ ##
...
checking for AL/al.h... no
checking for al.h... no
*** Hmm, you don't seem to have OpenAL headers installed in the standard
*** location (/usr/include). I'll check in /usr/local/include, since
*** many distributions put OpenAL headers there.
checking for AL/al.h... no
checking for al.h... no
Cannot find AL/al.h
Error::Configuring without OpenAL support!
No Crypto++ support
...
In file included from ../../../src/xml_support.h:11,
from ../../../src/faction_generic.h:5,
from comm_ai.cpp:2:
/usr/include/expat.h:657: use of enum `XML_Status' without previous declaration
/usr/include/expat.h:735: multiple definition of `enum XML_Status'
/usr/include/expat.h:657: previous definition here
make[4]: *** [comm_ai.o] Error 1
make[4]: Leaving directory `/root/vegastrike-0.4.1-installer/vegastrike/src/cmd/ai'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/root/vegastrike-0.4.1-installer/vegastrike/src/cmd'make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/root/vegastrike-0.4.1-installer/vegastrike/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/vegastrike-0.4.1-installer/vegastrike'
make: *** [all] Error 2
...
mv: cannot overwrite directory `/root/.vegastrike.3.x/.vegastrike'
mkdir: cannot create directory `/root/.vegastrike': File exists
mv: cannot stat `../vegastrike/src/vegastrike': No such file or directory
cp: cannot stat `../vegastrike/src/networking/soundserver': No such file or directory
cp: cannot stat `../vegastrike/launcher/vslauncher': No such file or directory
ok I need to be root now please enter your password (edit root-setup.sh to see what the script does if you are rightfully careful.)
/bin/bash: --command=../root-setup.sh: invalid option

then i run ./root-setup.sh:

root@darkstar:~/vegastrike-0.4.1-installer# ./root-setup.sh
install: cannot stat `./vegastrike': No such file or directory
install: cannot stat `./vslauncher': No such file or directory
mkdir: cannot create directory `/usr/local/man/man1': File exists
mkdir: cannot create directory `/usr': File exists
mkdir: cannot create directory `/usr/local': File exists
mkdir: cannot create directory `/usr/local/share': File exists
mkdir: cannot create directory `/usr/local/share/vegastrike': File exists
mv: cannot overwrite directory `/usr/local/share/vegastrike/data.bak/data'
mv: cannot overwrite directory `/usr/local/share/vegastrike/data'
run vsinstall to setup your account
then run vslauncher to start Vega Strike

then i run vsinstall:

root@darkstar:~/vegastrike-0.4.1-installer# vsinstall
mkdir: cannot create directory `/root/.vegastrike': File exists
default
readme.txt: No such file or directory
If you wish to have your own music edit ~/.vegastrike/*.m3u Each playlist represents a place or situation in Vega Strike

then i run vslauncher:

root@darkstar:~/vegastrike-0.4.1-installer# vslauncher
-bash: vslauncher: command not found

help me...tanks

[skilari]

Hiya

I'm getting almost _exactly_ the same output as you when I try to run setup.sh. So, I poked around with Google a bit and found out that at least the WARNINGS about the GL/glext.h supposedly are not autoconf problems but rather that of configure (found it in some autoconf mailing list by searching with one of those WARNING-lines). It's just kinda difficult to trace the problem with this installer package, IMHO.

Oh, and by the way, I do have the full stdout and stderr of setup.sh, but they are both >1000 lines long, so...

[unts]

how about rading this >>>> http://vegastrike.sourceforge.net/forum ... ht=glext+h

duh

[unts]

u have to be root also....