Woody compilings problems cpp0: output pipe has been closed

Trying to build your own version of Vega Strike and having problems? Unix users, paste your config.log here (stderr output alone is not helpful).
Post Reply
Guest

Woody compilings problems cpp0: output pipe has been closed

Post by Guest »

Hi, I downloaded the VS 4.1.tar.gz and started ./setup.sh. After installing the essential development packages libsdl1.2-dev libsdl1.2-mixer-dev openal-dev libgtk1.2-dev python2.2-dev libexpat1-dev xlibmesa-gl-dev glutg3-dev the compiler returns with the following message:

Code: Select all

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.2 -DHAVE_PYTHON=1  -DUSE_BOOST_129=1   -pipe -O3 -fexpensive-optimizations -fomit-frame-pointer -Wall -ffast-math   -I/usr/include/SDL -D_REENTRANT -pipe  -c hard_coded_scripts.cpp
In file included from ../../../src/python/python_class.h:24,
                 from hard_coded_scripts.cpp:9:
../../../src/python/init.h:30: `to_python_value' is not a template
../../../src/python/init.h:30: `detail' is not a class or namespace
../../../src/python/init.h:30: `builtin_to_python' is not a class or namespace
../../../src/python/init.h:30: confused by earlier errors, bailing out
cpp0: output pipe has been closed
make[4]: *** [hard_coded_scripts.o] Fehler 1
make[4]: Leaving directory `/usr/download/vegastrike-0.4.1-installer/vegastrike/src/cmd/ai'
make[3]: *** [all-recursive] Fehler 1
make[3]: Leaving directory `/usr/download/vegastrike-0.4.1-installer/vegastrike/src/cmd'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/usr/download/vegastrike-0.4.1-installer/vegastrike/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/usr/download/vegastrike-0.4.1-installer/vegastrike'
make: *** [all-recursive-am] Fehler 2
GCC Version: 2.95.4-11woody
CPP Version: 2.95.4-11woody
LIBC6-DEV Version: 2.2.5-11.5
G++ Version: 2.95.4-11woody
Surfdargent
Developer
Developer
Posts: 153
Joined: Wed Jan 22, 2003 4:28 am
Location: Reunion Island
Contact:

Post by Surfdargent »

You should try to call the configure script with "--enable-boost-128".
If this is the script that does it automatically, modify it to do so.
Guest

Post by Guest »

Ok I put it in the setup.sh

Code: Select all

#!/bin/sh
tar -zxf vegastrike-0.4.1-data.tgz
tar -zxf vegastrike-0.4.1-source.tgz
tar -zxf vegastrike-0.4.1-setup.tgz
cd vegastrike
aclocal
autoconf
automake -a
[b]./configure --enable-boost-128[/b]
make
cd ../vssetup/src/
perl ./build
cd ../../data
mkdir ~/.vegastrike
[...]
Guest

Post by Guest »

Ok, seems to work.
What means enable boost 128?
Surfdargent
Developer
Developer
Posts: 153
Joined: Wed Jan 22, 2003 4:28 am
Location: Reunion Island
Contact:

Post by Surfdargent »

It tells VS to use the 1.28 version of the boost lib instead of 1.29 which causes some problems with a bunch of compiler versions...
In fact, I would even suggest to make it the default.

HellCat : is there any reason why boost 1.29 is the default one ?
hellcatv
Developer
Developer
Posts: 3980
Joined: Fri Jan 03, 2003 4:53 am
Location: Stanford, CA
Contact:

Post by hellcatv »

well boost129 I thought only worked with gcc-3.2
but I think gcc-3.3 may work with both or only 128 so you're right it should be defauylt
Vega Strike Lead Developer
http://vegastrike.sourceforge.net/
Post Reply