Install errors at end of script (linux)

Just downloaded Vega Strike and need help? Have a question but don't know where to start? Ask here.
Post Reply
galorin
Star Pilot
Star Pilot
Posts: 4
Joined: Thu Jan 29, 2004 8:57 pm

Install errors at end of script (linux)

Post by galorin »

Here's he last few lines of the output from setup.sh. When trying to run the sudo section (in red) it can't do what it needs to do with the root-setup.sh script. When it hits the su section, it can't even find the ruddy file to execite it.. what's up here? I just decided to try the install from a cd on the front of a Linux Format magazine... and this is the result. If the setup.sh script needs editing, I just might be able to do that, but anything more.. I'm lost.

Linkingsh: line 1: gtk-config: command not found
g++: ../src/c/setup.o: No such file or directory
g++: ../src/include/central.o: No such file or directory
g++: ../src/include/display_gtk.o: No such file or directory
g++: ../src/include/file.o: No such file or directory
Done

Time Elapsed: 8 second
mv: cannot stat `/home/richard/.vegastrike': No such file or directory
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.)
Password:
../root-setup.sh: line 2: cd: data: No such file or directory
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': No such file or directory
install: cannot create regular file `/usr/local/man/man1/vegastrike.1': No such file or directory
install: cannot create regular file `/usr/local/man/man1/vslauncher.1': No such file or directory
install: cannot create regular file `/usr/local/man/man1/vsinstall.1': No such file or directory
install: cannot create regular file `/usr/local/man/man1/vssetup.1': No such file or directory
mkdir: cannot create directory `/usr': File exists
mkdir: cannot create directory `/usr/local': File exists
mkdir: cannot create directory `/usr/local/share': File exists
mv: cannot stat `/usr/local/share/vegastrike/data': No such file or directory
cp: cannot stat `data': No such file or directory
run vsinstall to setup your account
then run vslauncher to start Vega Strike
if you see a prompt now, that means you don't have su installed, type root password

Password:
bash: line 1: ../root-setup.sh: No such file or directory
[richard@fleur vegastrike-0.4.1-installer]$
Linux migration in progress, watch for falling penguins.
hellcatv
Developer
Developer
Posts: 3980
Joined: Fri Jan 03, 2003 4:53 am
Location: Stanford, CA
Contact:

Post by hellcatv »

try typing make inside the vegastrike/ directory
paste that output and where errors occur
Vega Strike Lead Developer
http://vegastrike.sourceforge.net/
galorin
Star Pilot
Star Pilot
Posts: 4
Joined: Thu Jan 29, 2004 8:57 pm

Post by galorin »

ok, here's the last few lines of utput from running make in the vegastrike directory.

There are quite a few more lines worth of the builtin_converters.hpp:113 error, don't know if you want all them or just where make hits it's errors.

`detail' is not a class or namespace
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: `builtin_to_python' is not a class or namespace
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: invalid base-class specification
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: can't make `operator()' into a method -- not in a class
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: `to_python_value' is not a template
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: `detail' is not a class or namespace
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: `builtin_to_python' is not a class or namespace
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: invalid base-class specification
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: can't make `operator()' into a method -- not in a class
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: `arg_to_python' is not a template
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: syntax error before `<' token
../../../src/boost129/boost/python/converter/builtin_converters.hpp:113: error: syntax error before `}' token
../../../src/boost129/boost/python/converter/builtin_converters.hpp:122: error: syntax error before `}' token
hard_coded_scripts.cpp: In constructor `Orders::LoopAround::LoopAround(bool, int)':
hard_coded_scripts.cpp:151: warning: comparison between signed and unsigned integer expressions
make[4]: *** [hard_coded_scripts.o] Error 1
make[4]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike/src/cmd/ai'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike/src/cmd'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike'
make: *** [all-recursive-am] Error 2
[richard@fleur vegastrike]$
Linux migration in progress, watch for falling penguins.
hellcatv
Developer
Developer
Posts: 3980
Joined: Fri Jan 03, 2003 4:53 am
Location: Stanford, CA
Contact:

Post by hellcatv »

looks like you have an old gcc try this
./configure --enable-boost-128
make

and see if that fixes it

if not try
./configure --enable-boost-129
make

nto sure which is the default these days
Vega Strike Lead Developer
http://vegastrike.sourceforge.net/
galorin
Star Pilot
Star Pilot
Posts: 4
Joined: Thu Jan 29, 2004 8:57 pm

Post by galorin »

with --enable-boost-128 and --enable-boost-129 gives the following error, though it did seem to get past the earlier error section.

c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src -I../../src/boost129 -DHAVE_SDL=1 -DSDL_WINDOWING=1 -DHAVE_SDL_MIXER=1 -DHAVE_AL=1 -I/usr/include/python2.3 -DHAVE_PYTHON=1 -DUSE_BOOST_129=1 -pipe -O2 -fexpensive-optimizations -fomit-frame-pointer -Wall -ffast-math -I/usr/include/SDL -D_REENTRANT -pipe -c gl_init.cpp
gl_init.cpp: In function `void init_opengl_extensions()':
gl_init.cpp:106: error: `glXGetProcAddressARB' undeclared (first use this function)
gl_init.cpp:106: error: (Each undeclared identifier is reported only once for each function it appears in.)
../../src/cmd/collection.h: At global scope:
../../src/cmd/collection.h:49: warning: inline function `void UnitCollection::UnitIterator::GetNextValidUnit()' used but never defined
make[3]: *** [gl_init.o] Error 1
make[3]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike/src/gldrv'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/richard/vegastrike-0.4.1-installer/vegastrike'
make: *** [all-recursive-am] Error 2
[richard@fleur vegastrike]$
Linux migration in progress, watch for falling penguins.
hellcatv
Developer
Developer
Posts: 3980
Joined: Fri Jan 03, 2003 4:53 am
Location: Stanford, CA
Contact:

Post by hellcatv »

everyone's having the glXGetprocAddressARB
someone in Mesa changed the header or the .so to have the wrong name for this function
you can use a
#define glXGetProcAddressARB glXGetProcAddress
or vice versa in one of the files
there is plenty of help on this particular subject on the forum or the wiki
Vega Strike Lead Developer
http://vegastrike.sourceforge.net/
galorin
Star Pilot
Star Pilot
Posts: 4
Joined: Thu Jan 29, 2004 8:57 pm

Post by galorin »

Thanks for that, although I seem to have run into another problem that will need resolving, which is not connected to vegastrike. Ever since I went to Mandrake 9.2 (dialup, and got both MDK and VS off a magazine cover, might get rpm's as last resort) trying to use the nvidia drivers locks up my system. Works fine in Slackware, and MDK9.1, but not 9.2 for some reason that I need to figure out. Until I get this resolved, not much point in trying to get VS installed.
Linux migration in progress, watch for falling penguins.
Post Reply