Author Topic: cant install correctly...  (Read 1838 times)

dgart

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
cant install correctly...
« on: January 31, 2005, 04:30:02 pm »
i cant start planshift after installing... my libcurl is insatlled correctly.
im using suse 9.2.

thx for replies.

We are now going to configure Planeshift.

New install dir (it will be created).
/usr/local/games/planeshift
Are you a developer? (No)
No
Do you also want to update the client? (No)
No
Are you using a Amd64 processor? (No)
No
What is your Linux account name? (Not Planeshift related)
ceberus
What is your group name?
users
Configuration done.

It will take alot of time to install planeshift by source.
So you can do something else in the meantime.
The installer will do the rest by it self.

Decompressing files.
All files decompressed.

Starting installing files.
This can take alot of time.

Installing Cal3d.
Installing Cal3d..
Installing Cal3d...

Installing Crystal Space.
Installing Crystal Space..
Installing Crystal Space...

Installing Cel.
Installing Cel..
Installing Cel...

Installing Planeshift.
Installing Planeshift..
Installing Planeshift...
Installing Planeshift....
Creating executebles.
./update: line 5: ./updater: Datei oder Verzeichnis nicht gefunden
Installation is complete.

Karosh_Steinkatz

  • Hydlaa Citizen
  • *
  • Posts: 486
    • View Profile
(No subject)
« Reply #1 on: January 31, 2005, 04:52:39 pm »
That\'s not very much info. Can you post the install log? I think it\'s called install_full.log.


Back to Planeshift again \\o/

dgart

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #2 on: January 31, 2005, 07:32:12 pm »
no problem, but too much text...

Configuration done.
Planeshift dir created
All files decompressed.
Installing Cal3d.
Running \'aclocal-1.9 \'
Running \'autoheader\'
Running \'libtoolize --force\'
Running \'automake-1.9 --add-missing --force-missing --copy\'
configure.in: installing `./install-sh\'
configure.in: installing `./missing\'
src/cal3d/Makefile.am: installing `./depcomp\'
Running \'autoconf \'

Now run ./configure and make.

checking build system type... i686-suse-linux
checking host system type... i686-suse-linux
checking target system type... i686-suse-linux
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether user defined C++ flags overwrite the default Cal3D ones... no
checking for g++... g++
checking for C++ compiler default output file name... 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 g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /usr/bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag  works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag \"CXX\" to libtool
checking for ld used by g++... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag \"F77\" to libtool
checking for a BSD-compatible install... /usr/bin/install -c
checking for doxygen... true
checking for db2html... true
checking whether to build Cal3D in debug mode... no
checking whether g++ supports -fno-rtti... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/cal3d/Makefile
config.status: creating docs/Makefile
config.status: creating docs/api/Makefile
config.status: creating docs/shared/Makefile
config.status: creating cal3d.pc
config.status: creating config.h
config.status: executing depfiles commands
o-----------------------------------------------------------o
| To build and install the Cal3D library type...            |
|     make; make install                                    |
|                                                           |
| To generate the Cal3D User\'s Guide type...                |
|     cd docs; make doc-guide                               |
|                                                           |
| To generate the Cal3D API Reference type...               |
|     cd docs; make doc-api                                 |
o-----------------------------------------------------------o

\"SHORTED ==>TOO LONG\"

----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/games/planeshift/cal3d/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR\'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH\' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH\' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR\' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf\'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------

SHORTED

----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/games/planeshift/cal3d/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR\'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH\' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH\' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR\' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf\'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------

SHORTED


configure: WARNING: Can not find cs-config in path you provided
no
configure: error:
*** Crystal Space could not be found. The latest version is always available
*** from http://www.crystalspace3d.org/
*** Also, be sure that you have either installed Crystal Space or set the
*** CRYSTAL environment variable properly.

./planeshift_CBV0.3.006.sh: line 274: jam: command not found
Installing Planeshift.
Creating a configure file...
Now ready to ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... 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 accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking if -shared is accepted... -shared
checking if -soname is accepted... yes
checking for install... install
checking for ranlib... ranlib
checking how to run the C preprocessor... gcc -E
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for socklen_t... yes
checking for stdint-types... found in stdint.h
creating include/psstdint.h - (just to include  stdint.h)
configure: WARNING: Can not find cs-config in path you provided
no
configure: error:
*** Crystal Space could not be found. The latest version is always available
*** from http://crystal.sourceforge.net/
*** Be sure also that you have either installed Crystal Space or set the
*** CRYSTAL environment variable properly.

./planeshift_CBV0.3.006.sh: line 300: jam: command not found
./planeshift_CBV0.3.006.sh: line 302: jam: command not found
./planeshift_CBV0.3.006.sh: line 302: jam: command not found
Creating executebles.
Installation is complete.

dgart

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #3 on: January 31, 2005, 07:34:48 pm »
after installation i cant find the updater or any other binarys to start the game...

use used http://www.holarse.de  as source...

Androgos

  • Guest
(No subject)
« Reply #4 on: January 31, 2005, 07:40:59 pm »
You need jam

dgart

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #5 on: January 31, 2005, 09:59:03 pm »
installation worked now, thanks, but now...

...ive tried:

/usr/local/games/planeshift/planeshift/updater --auto

and got

WARNING: could not load plugin \'crystalspace.kernel.vfs\'
Couldn\'t load VFS plugin \"crystalspace.kernel.vfs\"!
ERROR: csInitializer::SetupConfigManager failed!
Is your CRYSTAL environment variable set?

message...

Karosh_Steinkatz

  • Hydlaa Citizen
  • *
  • Posts: 486
    • View Profile
(No subject)
« Reply #6 on: January 31, 2005, 11:25:27 pm »
Hmm, wasn\'t the name of the updater start script \'update\'? Try that, because if you run the binary directly, it complains about missing exports which are set in that script.


Back to Planeshift again \\o/

dgart

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #7 on: February 01, 2005, 12:07:18 pm »
no \"updater\"... pssetup also dont work too. and i get also the same error message.

alienjon

  • Traveller
  • *
  • Posts: 11
    • View Profile
(No subject)
« Reply #8 on: April 30, 2005, 11:41:06 pm »
same issue here. I\'m using gentoo and went throught the help file step by step on the planeshift site. I can\'t run the binary at all (or the setup for that matter either) I get:

bash: psclient: command not found

Still browsing the forum, but any ideas?

Androgos

  • Guest
(No subject)
« Reply #9 on: May 01, 2005, 12:03:12 am »
do echo $CRYSTAL and echo $CEL and post it\'s output

also, try to run the executables from it\'s directory

alienjon

  • Traveller
  • *
  • Posts: 11
    • View Profile
(No subject)
« Reply #10 on: May 03, 2005, 04:38:31 am »
Well, the two variables did not, in fact, set up correctly. While I was looking into the problem, I noticed that I had accidentily installed something in the wrong place (just a bad day, I guess :-/) Regardless, I re-installed the game and the error went away. Now I have the update problem, which I\'m pretty sure I saw somewhere else on the forum so I\'ll just save the space here. Thanks for the tip on where to look.