PlaneShift

Support => Technical Help: Problems BEFORE entering the game => Topic started by: Sharaz on April 29, 2003, 01:53:02 am

Title: How's the PS Linux Source Package coming along?
Post by: Sharaz on April 29, 2003, 01:53:02 am
Some time ago Atanor said that he was working on a source version of 0.2.010 for Linux, besides the current binary version.
Since then I haven\'t read any more news about it, so i was wondering if anybody knows what\'s going on.
Atanor, have you got any news for us, please?
Title:
Post by: hook on April 29, 2003, 02:00:12 am
did you try the CVS tree?
Title:
Post by: Sharaz on April 29, 2003, 02:22:14 am
I\'ve had some problems with that. Most of them I was able to fix, but in the end there were still a few that drove me completely nuts. And I have already got (medium) experience with CVS and compiling my own programs. A good package would make PS much more available to ,slightly less experienced, Linux users.

I also believe that it\'s important that it\'s a source package, since binary packages tend to give problems on machines that use slightly different libraries. That\'s the problem with the current binary package. It\'s compiled agains the very latest (bleeding edge) libc6, which isn\'t in Debian Unstable yet.
Title:
Post by: Kundalf on April 29, 2003, 12:36:39 pm
hey folks,

afaik the source packages are already ready for d/l on downloads (http://www.planeshift.it/download_source.html)
I guess one of the packages was broken in the beginning, but as far as I could see its fixed now.

In my opinion a binary package is more important, since you can download the sources from cvs (which should be the same as in the package if you take the MB release). The librarys, cs, cel etc can either be taken from cvs or from your distribution.

But it would make sense to build a statically liked package, although it may be a lot bigger. Maybe using non bleeding edge librarys for compilation would make it easyer to install the binaries for ppl using non state of the art distributions.

(bleeding edge may be a little exaggerated :D but I hope you understand what I mean anyways...;))

Title:
Post by: Sharaz on April 29, 2003, 02:11:03 pm
I\'ve just begun to build the source packages and I got an error when running \'./configure\' in the CS dir:

mk/subs.mak:30: docs/docs.mak: No such file or directory
mk/subs.mak:30: docs/docs.mak: No such file or directory
make: *** No rule to make target `docs/docs.mak\'.  Stop.

It doesn\'t appear to be fatal, but it would be better if it were fixed.

Now about the source package.
The source package should contain everything you need to run PS, no more, no less. The problems with getting CP, CEL and PS from CVS are:
1) You\'re often downloading more than you need.
2) Since you\'re using the latest of all 3 programs, there\'s a much higher chance of bugs.
3) Except for the forum, there\'s little documentation on how to get the 3 parts running together. This makes it a lot harder for newbies.

It would be very nice if there were a source package that has been tested and is easy to install.

Binary packages however have some inherent flaws.
1) They\'re not optimized for your system.
2) They\'re bigger
3) They\'re sometimes compiled against libs that are much newer than is neccesary. (The current problem....)

All in all, I still believe that a source package is a good idea. I\'ll  test the current one and post my findings to the board.
Title:
Post by: Sharaz on April 29, 2003, 02:49:47 pm
Ok the first problem was easily fixed. Since docs/docs.mak doesn\'t excist, remove it as a target from mk/subs.mak.

New problem building Crystal Space from the provided package:
plugins/aws/slp.hpp is needed but doesn\'t exist.
I checked the CS CVS, but it isn\'t in their repository either anymore.
Title:
Post by: Kundalf on April 29, 2003, 03:18:34 pm
Quote
1) They\'re not optimized for your system.


Usually none of the packages your distribution uses is optimized for your system, so an unoptimized PS will only make a minor difference...;)


Quote
2) They\'re bigger
3) They\'re sometimes compiled against libs that are much newer than is neccesary. (The current problem....)


Thats what I said b4...:D
Title:
Post by: Kundalf on April 29, 2003, 03:26:26 pm
Quote
Originally posted by Sharaz
Ok the first problem was easily fixed. Since docs/docs.mak doesn\'t excist, remove it as a target from mk/subs.mak.


hmm, I\'ve already got my PS running, but I just thought try to compile the source packages...;)

So try to use configure-jam instead of configure. It works for me without glitches or errors so far.
Title:
Post by: Sharaz on April 29, 2003, 04:03:06 pm
With jam I get a problem with the same part of the compilation:

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)...

This is in the same plugin that broke the normal compile.
Title:
Post by: Kundalf on April 29, 2003, 04:23:49 pm
have you copied the cs-config script into your cel source directory ?...;)
Title:
Post by: Sharaz on April 29, 2003, 05:27:44 pm
I will, once I manage to compile CS :)
I\'m still having bugs when compiling CS, all centered around \'aws\', probably about the missing slp.hpp.

It doesn\'t matter wether I use jam or compile normally.
Title:
Post by: Kundalf on April 29, 2003, 05:41:24 pm
do you have icq or something ?
You may try to visit irc...
Title:
Post by: Sharaz on April 29, 2003, 07:31:36 pm
Jabber: bas@luon.net
ICQ (since today): bas@meteoor.net

I couldn\'t reach the irc, I got a timeout.
Title:
Post by: Atanor on April 30, 2003, 09:00:31 pm
Sorry for not posting it before!!!! (read the README.txt)


http://prdownloads.sourceforge.net/planeshift/planeshift-0.2.010FullSourceAndArt.tar.gz?downloadhif
Title:
Post by: Sharaz on May 01, 2003, 06:45:26 pm
Ok, I\'ll try it right now. I\'m very anctious to see PS for real :)  
Title:
Post by: Sharaz on May 01, 2003, 07:09:48 pm
Ok, this is what goes wrong:

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)...

Hope you can give me some tips. I\'ll come by in IRC as well if I have the chance.
Title:
Post by: Fextina on May 02, 2003, 02:21:47 pm
Ok, I had the same problems as Sharaz

What I did was to edit skinpars.yy and remove the extra item

it should become

%type      skin_item window_item component_item connection_item


(window_item) was repeated twice there.

After that, I recompiled and I got PS to work for the first time in quite a while!

I also did somehting else but don\'e exactly remember it, it was related to skinpars.cpp required (but only skinpars.hpp was available) I guess.
Title:
Post by: Sharaz on May 02, 2003, 02:25:18 pm
I fixed the first part with the help of Atanor last night. But if you could remember what you did to fix the second problem I\'d be very grateful. That\'s the one that\'s stopping me from playing PS.
Title:
Post by: Fextina on May 03, 2003, 06:40:36 am
Well, why didn\'t you ask Atanor to solve the 2nd problem then? :)

I\'ll try to rebuild it again and see what I did.
Title:
Post by: montypythonite on June 24, 2003, 10:22:25 am
This problem is apparently caused by missing a file (CS/plugins/aws/skinlex.cpp).  I was able to fix the problem by downloading the missing file from CrystalSpace\'s CVS.
Here is a link to the missing file on the SourceForge Web frontend:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/crystal/CS/plugins/aws/skinlex.cpp

Click \"(download)\" and save the link to disk in the appropriate directory.  As of today, the newest version on the CVS is the same  version that should have been included in the tarball from PS.

It still isn\'t working for me, but the buck has been passed (I think it may just be a question of libraries installed/header files, but it may be impossible to get it to work on my install due to some dependency issues with sarge that have been around for over a month now but no one seems to care)
Title:
Post by: Sharaz on June 24, 2003, 01:02:10 pm
I\'ve finally managed to get PS to work under Debian SID, here\'s what I did:
I followed acraig\'s guide to building PS from CVS for Linux, with the following extra\'s:

1) Use flex-old and bison 1.35 (as entioned in the guide)
2) Compile using gcc/g++ 3.2, you can do this by adding CC=gcc-3.2 CXX=g++-3.2 CPP=cpp-3.2 to each configure you have to do.

That works for me, hope it works for you too. :)
Title:
Post by: angmar on July 06, 2003, 04:54:45 am
I have a Debian Sid box and a did all the step of the site:

http://www16.brinkster.com/acraig/planeshift/buildmb.html

The CS and cel compiled very nice.

But, when I compile the planeshift package from CVS I got:

...failed updating 56 target(s)...
...skipped 11 target(s)...

and

ldd psclient-bin
./psclient-bin: /lib/libpthread.so.0: version `GLIBC_2.3.2\' not found (required by ./psclient-bin)
 libdl.so.2 => /lib/libdl.so.2 (0x40024000)
  libnsl.so.1 => /lib/libnsl.so.1 (0x40027000)
    libpthread.so.0 => /lib/libpthread.so.0 (0x4003a000)
    libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40089000)
  libm.so.6 => /lib/libm.so.6 (0x40135000)
    libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40156000)
    libc.so.6 => /lib/libc.so.6 (0x4015e000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)