Page 1 of 1

Compile problem (python?)

Posted: Sun Feb 06, 2005 10:50 pm
by Azzie
Ive been trying to compile from cvs using the linux_vegastrike-0.4.2.sh install script for a few days now and everytime, it fails in the same place whether I add --enable-boost-128 to the configure line or not, here is where it dies:

Code: Select all

Making all in python
make[3]: Entering directory `/root/vegastrike_0_4_2/vegastrike/src/python'
if g++ -DHAVE_CONFIG_H -I. -I. -I../..   -DHAVE_SDL=1 -DSDL_WINDOWING=1      -DHAVE_AL=1   -I/usr/include/python2.3 -DHAVE_PYTHON=1  -DUSE_BOOST_128=1 -I../../src/boost  -I../../src   -pipe  -O2 -ffast-math -falign-loops=2 -falign-jumps=2 -falign-functions=2  -I/usr/include/SDL -D_REENTRANT -pthread -pipe -MT init.o -MD -MP -MF ".deps/init.Tpo" -c -o init.o init.cpp; \
then mv -f ".deps/init.Tpo" ".deps/init.Po"; else rm -f ".deps/init.Tpo"; exit 1; fi
In file included from /usr/include/python2.3/Python.h:8,
                 from init.cpp:5:
/usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/stdio.h:28,
                 from init.cpp:3:
/usr/include/features.h:131:1: warning: this is the location of the previous definition
if g++ -DHAVE_CONFIG_H -I. -I. -I../..   -DHAVE_SDL=1 -DSDL_WINDOWING=1      -DHAVE_AL=1   -I/usr/include/python2.3 -DHAVE_PYTHON=1  -DUSE_BOOST_128=1 -I../../src/boost  -I../../src   -pipe  -O2 -ffast-math -falign-loops=2 -falign-jumps=2 -falign-functions=2  -I/usr/include/SDL -D_REENTRANT -pthread -pipe -MT python_compile.o -MD -MP -MF ".deps/python_compile.Tpo" -c -o python_compile.o python_compile.cpp; \
then mv -f ".deps/python_compile.Tpo" ".deps/python_compile.Po"; else rm -f ".deps/python_compile.Tpo"; exit 1; fi
In file included from /usr/include/python2.3/Python.h:8,
                 from python_compile.h:4,
                 from python_compile.cpp:2:
/usr/include/python2.3/pyconfig.h:850:1: warning: "_POSIX_C_SOURCE" redefined
In file included from /usr/include/math.h:27,
                 from ../../src/hashtable.h:25,
                 from ../../src/cmd/unit_generic.h:28,
                 from python_compile.cpp:1:
/usr/include/features.h:131:1: warning: this is the location of the previous definition
python_compile.cpp: In function `void pySetScratchVector(KBSTATE)':
python_compile.cpp:113: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp:116: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp:119: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp:122: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp: In function `void RunPythonPress(const KBData&, KBSTATE)':
python_compile.cpp:132: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp: In function `void RunPythonRelease(const KBData&, KBSTATE)
   ':
python_compile.cpp:139: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp: In function `void RunPythonToggle(const KBData&, KBSTATE)':
python_compile.cpp:146: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
python_compile.cpp: In function `void RunPythonPhysicsFrame(const KBData&,
   KBSTATE)':
python_compile.cpp:154: error: `setScratchVector' undeclared in namespace `
   UniverseUtil'
make[3]: *** [python_compile.o] Error 1
make[3]: Leaving directory `/root/vegastrike_0_4_2/vegastrike/src/python'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/root/vegastrike_0_4_2/vegastrike/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/vegastrike_0_4_2/vegastrike'
make: *** [all] Error 2
Error running 'make'

Posted: Mon Feb 07, 2005 8:23 am
by hellcatv
that looks like an error that's months and months old...which compiler is this? are you sure you updated cvs? what age is this cvs tree from

Posted: Mon Feb 07, 2005 8:58 am
by Ari Rahikkala
Um... I'm pretty sure this is from the vegastrike_0_4_2 tag, if llinux_vegastrike-0.4.2.sh is what the original poster used :)

Posted: Mon Feb 07, 2005 1:27 pm
by Azzie
hellcatv wrote:that looks like an error that's months and months old...which compiler is this? are you sure you updated cvs? what age is this cvs tree from
its gcc 3.3.5

I havent modified the script apart from adding the --enable-boost-128 to the configure line to see if that was the problem, so the script should be updating from cvs correctly, unless something is borked on my end or the cvs end.

I guess ill play around with it tomorrow.

Posted: Tue Feb 08, 2005 3:56 am
by hellcatv
you can try
cvs update -A
from the source dir

Posted: Tue Feb 08, 2005 6:02 am
by Azzie
sorry didnt see that you replied

I just deleted the directory and ran the script again and this time it worked, I dont know what was up on my end but I dont really care now, thanks for your help :)