Author Topic: some problem with linux  (Read 1466 times)

il_guru

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
some problem with linux
« on: August 14, 2003, 11:33:18 pm »
hi, i\'m a newbie, i tried to run planeshift bye binaries but i get an error like this (i paste from another post)

\"mercy@blubber:~/Entpack/planeshift> ./psclient -verbose
Warning: Failed to load `gl3d\'; use \'-verbose\' argument for details.
Warning: Failed to load `gl3d\'; use \'-verbose\' argument for details.
WARNING: could not load plugin \'crystalspace.graphics3d.opengl\'
aws-debug: Couldn\'t find iGraphics2D plugin!!
psclient: No 3d driver (iGraphics3D) plugin!
mercy@blubber:~/Entpack/planeshift> \"

but my nvidia drivers works good with other 3d games like enemy territory...
so i decided to try compile the source ... i read the readme that told me to run build.sh...
i run build.sh but receive this error...

configure-jam: creating ./config.status
config.status: executing include/volatile.h commands
config.status: include/volatile.h is unchanged
config.status: executing Jamconfig commands
config.status: Jamconfig is unchanged
config.status: executing Jamfile commands
config.status: executing test commands
data/Jamfile: No such file or directory
plugins/cssaver/Jamfile: No such file or directory
apps/Jamfile: No such file or directory
...patience...
...patience...
...found 2485 target(s)...
...updating 5 target(s)...
Flex plugins/aws/skinlex.cpp
flex: fatal internal error, bad line in skeleton file

    flex -S./mk/support/flex.skl -t  plugins/aws/skinlex.ll > plugins/aws/skinlex.cpp

...failed Flex plugins/aws/skinlex.cpp ...
...removing plugins/aws/skinlex.cpp
...skipped skinlex.o for lack of skinlex.cpp...
Bison plugins/aws/skinpars.cpp
plugins/aws/skinpars.yy:61.8-12: type redeclaration for window_item

    bison -d -p aws -o plugins/aws/skinpars.cpp plugins/aws/skinpars.yy

...failed Bison plugins/aws/skinpars.cpp ...
...skipped skinpars.o for lack of skinpars.cpp...
...skipped aws.so for lack of skinlex.o...
...failed updating 2 target(s)...
...skipped 3 target(s)...


i really don\'t understand what i have to do... can you help me?

il_guru

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #1 on: August 14, 2003, 11:43:59 pm »
ups i read now the lines about debian...so i install the right flex and bison but now i\'ve another similar error...


configure-jam: creating ./config.status
config.status: executing include/volatile.h commands
config.status: include/volatile.h is unchanged
config.status: executing Jamconfig commands
config.status: Jamconfig is unchanged
config.status: executing Jamfile commands
config.status: executing test commands
data/Jamfile: No such file or directory
plugins/cssaver/Jamfile: No such file or directory
apps/Jamfile: No such file or directory
...patience...
don\'t know how to make skinpars.cpp
...patience...
...found 2481 target(s)...
...can\'t find 1 target(s)...
...can\'t make 2 target(s)...
...skipped skinpars.o for lack of skinpars.cpp...
...skipped aws.so for lack of skinpars.o...
...skipped 2 target(s)...

il_guru

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #2 on: August 15, 2003, 11:50:37 am »
well
another little problem....

now the build.sh arrives to build CEL, but when it start i receive an error from the pythont version that previously was recognized right!
i have python2.3 but it tells me that my python is too old (serching for some older than 1.5.....) i really can\'t understant the problem!

i past here what it says...

Quote

ilguru@debian:~/my_planeshift$ sh build.sh
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc-3.2
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc-3.2 accepts -g... yes
checking for gcc-3.2 option to accept ANSI C... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether g++-3.2 accepts -g... yes
checking for flex... flex
checking for bison... bison-1.35
checking for doxygen... no
checking for texi2dvi... texi2dvi
checking for texi2pdf... no
checking for install... install
checking for ranlib... ranlib
checking for swig... no
checking for luaswig... no
checking how to create a directory... mkdir
checking how to create a directory tree... mkdir -p
checking for nasm... nasm
checking for nasm extensions... yes
checking for perl5... no
checking for perl... perl
checking for perl ExtUtils::Embed module... yes
checking for perl DynaLoader module... yes
checking for python... python2.3
checking for Python SDK... yes
checking if Python SDK is usable... yes

checking how to enable compilation warnings... -Wall
checking how to treat warnings as errors... -Werror
checking how to disable unknown #pragma warnings... -Wno-unknown-pragmas
checking how to disable C++ exceptions... -fno-exceptions
checking if -multiply_defined suppress is needed... no
checking whether to use CPU-specific instructions... yes
checking for code generation flags... -mcpu=pentiumpro -march=i686
checking how to enable optimizations... -O3
checking if g++-3.2 recognizes -fomit-frame-pointer... -fomit-frame-pointer
checking if g++-3.2 recognizes -ffast-math... -ffast-math
checking how to enable compiler debug output... -g3
checking checking if -I/usr/local/include is usable... yes
checking for pow in -lm... yes
checking for dlopen in -ldl... yes
checking for gethostbyname in -lnsl... yes
checking for pthread... yes
checking for pthread recursive mutexes... PTHREAD_MUTEX_RECURSIVE
checking how to run the C preprocessor... cpp-3.2
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for libXxf86vm... yes
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for int32... no
checking for windows.h... no
checking for OpenGL... yes
checking for GLU... yes
checking for glut... no
checking for GLX... yes
checking for GLX extensions... yes
checking for libz... yes
checking for libpng... yes
checking for libjpeg... yes
checking for libmng... yes
checking for libmikmod... no
checking for libogg... yes
checking for libvorbis... yes
checking for libvorbisfile... yes
checking for lib3ds... no
checking for libode... no
checking for OpenAL... no
checking for freetype-config... /usr/bin/freetype-config
checking for FreeType - version >= 2.0... yes
checking for libvga... no
checking for libcal3d... no
checking if plugins require main()... yes
checking whether byte ordering is bigendian... no
checking for bool... yes
checking for stdint.h... (cached) yes
checking whether INT64_C works... yes
checking soundcard.h usability... no
checking soundcard.h presence... no
checking for soundcard.h... no
checking sys/soundcard.h usability... yes
checking sys/soundcard.h presence... yes
checking for sys/soundcard.h... yes
checking for unistd.h... (cached) yes
checking for sys/types.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking winsock.h usability... no
checking winsock.h presence... no
checking for winsock.h... no
checking for socket support... yes
checking for socklen_t... yes
checking for C++ `explicit\' keyword... yes
checking for C++ new-style casts... yes
checking if qsqrt() is usable... no
checking if qint() functions correctly... no
checking whether to enable Linux joystick support... no
checking build mode... optimize
checking if building plugins... yes
checking if enforcing smart pointer strictness... yes
checking whether to use extensive memory debugger... no
configure-jam: creating ./config.status
config.status: executing include/volatile.h commands
config.status: include/volatile.h is unchanged
config.status: executing Jamconfig commands
config.status: Jamconfig is unchanged
config.status: executing Jamfile commands
config.status: executing test commands
data/Jamfile: No such file or directory
plugins/cssaver/Jamfile: No such file or directory
apps/Jamfile: No such file or directory
...patience...
...patience...
...found 2520 target(s)...
data/Jamfile: No such file or directory
plugins/cssaver/Jamfile: No such file or directory
apps/Jamfile: No such file or directory
...found 5 target(s)...
BUILDING CEL NOW
creating aclocal.m4 from macros out of mk/*.m4
autoconf
checking for gcc... gcc-3.2
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc-3.2 accepts -g... yes
checking for gcc-3.2 option to accept ANSI C... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether g++-3.2 accepts -g... yes
checking for jam... jam
checking for Crystal Space - version >= 0.96... crystal 0.97
checking how to run the C preprocessor... cpp-3.2
checking for python... /usr/bin/python
checking if Python version >= 1.5... configure: error: too old



note that the first time he correctly recognize python! but not the second time building CEL... could someone help me???

tangerine

  • Hydlaa Resident
  • *
  • Posts: 192
    • View Profile
(No subject)
« Reply #3 on: August 15, 2003, 11:56:17 pm »
If you want to solve the python thing, open config.log file (that was generated by configure) and you may find the answer there.

il_guru

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #4 on: August 16, 2003, 02:35:57 pm »
i can only found this about python

configure:3065: checking for python
configure:3083: found /usr/bin/python
configure:3095: result: /usr/bin/python
configure:3104: checking if Python version >= 1.5
Traceback (most recent call last):
  File \"\", line 7, in ?
  File \"/usr/lib/python2.3/string.py\", line 220, in atoi
    return _int(s, base)
ValueError: invalid literal for int(): 3+
configure:3123: error: too old

it\'s no a lot....
it seems like he can\'t convert the version number...
any suggestions?

tangerine

  • Hydlaa Resident
  • *
  • Posts: 192
    • View Profile
(No subject)
« Reply #5 on: August 16, 2003, 04:22:49 pm »
The /usr/bin/python binary is probably the old version of python. You may symlink a 2.3 version binary to /usr/bin/python  so it is used by default.

Kundalf

  • Hydlaa Resident
  • *
  • Posts: 175
    • View Profile
(No subject)
« Reply #6 on: August 17, 2003, 10:14:31 am »
but beware of deleting the old file. Who knows which application needs the old one....;)
-- take care --
 

visit my favored site  ;)

il_guru

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #7 on: August 17, 2003, 11:02:36 am »
first of make the symlink i tried to discover what my /usr/bin/python is...

ilguru@debian:~$ file /usr/bin/python
/usr/bin/python: symbolic link to `python2.3\'


ehm....
well i think i\'ll try to make a symlink to python2.2 ...

il_guru

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #8 on: August 17, 2003, 11:08:10 am »
nothing... also with 2.2 i receive the same error!

PlugZ

  • Wayfarer
  • *
  • Posts: 1
    • View Profile
(No subject)
« Reply #9 on: September 24, 2003, 03:34:12 pm »
Hey

I\'ve had the same problem with the cel configure script.
I think the problem is the \'+\' sign appended to the python version number.
I couldn\'t figure out how to change it properly so I modified the base of the configure script so the test always returns true.

All you have to do is comment out (using #) the lines 57, 58, 60, 61, 62 in the python.m4 file which is located in cel/mk/

Once this is done, launch the build.sh script and here you go ! :)

The rest should go fine (it did for me)

Good luck.