PlaneShift

Support => Technical Help: Problems BEFORE entering the game => Topic started by: uafr on April 14, 2003, 11:52:22 pm

Title: Linux Binary PSV0.2.010.tar.gz
Post by: uafr on April 14, 2003, 11:52:22 pm

According to the homepage the binary linux distribution was
tested (among others) on Debian Woody. I tried it with
Debian Sarge.

First Problem: missing xwin.so
Fix: copy xwin.so from old version.
 
Next Problem:
./psclient-bin: /lib/libpthread.so.0: version `GLIBC_2.3.2\' not found (required by ./psclient-bin)

Now thats difficult: Glibc 2.3.2 is really new. There is not even a
Package for Debian unstable. How could they test it with Woody?
Any Ideas?

Title:
Post by: Atanor on April 15, 2003, 08:14:01 am

I made the package. In fact, I realized after that that I did compile 2.3.2 on my Debian Woody, that\'s why I had no problem when I tested it.
The problem is that Linux world is splitted in two: those who are running 2.2 and lesser and ther others...

I am currently downgrading my Debian in order to make a package for people who have older versions of glibc... But it won\'t be a official and supported package I think...

Title:
Post by: Atanor on April 15, 2003, 08:17:24 am

\"First Problem: missing xwin.so
Fix: copy xwin.so from old version. \"

Hmm, i have uncompressed my archive several times... xwin.so is there... Anyone else misses xwin.so ?

Title:
Post by: Sharaz on April 15, 2003, 10:36:30 am

First of all, thanks for building the Linux version. :D

Now for the problems....:)
I don\'t have any problem with xwin.so, it\'s definately in the package.

Now for the glibc problem. The glibc version in Debian Unstable is 2.3.1, so in my opinion there are a couple of probable sollutions for the official Linux version.

1) Change the supported systems text from Debian Woody to Debian Sarge and recompile PS with 2.3.1 This would definitely be the one I prefer.
2) Change the supported systems text from Debian Woody to Debian Sarge and wait till 2.3.2 comes into Debian. That\'s the least work for everybody and what I\'ll probably do if a recompiled version doesn\'t come out.
3) Recompile it against 2.2.5 (Woody glibc version). I\'d save this one for an inofficial version, as you\'ve already suggested.

I\'ll definately be monitoring the forum to see what\'s gonna happen. :)

Title:
Post by: Atanor on April 15, 2003, 10:41:27 am

You welcome  :)

If you are interested, we can work together to make a special version for people with an old glibc...

Title:
Post by: Sharaz on April 15, 2003, 02:02:26 pm

I tried to compile the CVS version some time ago and it was a pain in the a$$, since I don\'t have (easy) root access on the machine I\'m working on. Since CEL (if I remember correctly) simply refused to look for it\'s libs in the directory I specified, I finally gave up. And I used every option in the config / EXPORT I could think of.

I do have my own machine running Debian Sarge, but that\'s a P233 notebook, so compiling on this machine is simply impossible.

I\'d be happy to work together on a (Debian) Linux version, but since I\'d have to work together with the sysadmin of the machine (who happens to be a good friend of mine) it will take a little more time.

If you\'re still interested in working together, just send me a PM.

Title:
Post by: Atanor on April 15, 2003, 02:04:58 pm

Hmm, no need to be a system admin to compile planeshift/CS/CEL ...

but we will need \'jam\' and developpement packages for ogg vobis and all...

Title:
Post by: uafr on April 15, 2003, 02:33:13 pm

Quote

Originally posted by Atanor
The problem is that Linux world is splitted in two: those who are running 2.2 and lesser and ther others...

What about a static version like 0.2.006?

By the way: I checked the Package for  xwin.so. It is included,
but uses  
libXxf86vm.so.1 => not found

The old xwin.so works without that lib so I can run pssetup.
Where can I get libXxf86vm?

I tried again to compile planeshift myself from CVS, but that does not work either. (It compiles, but the Programm does not run.)

Title:
Post by: Atanor on April 15, 2003, 02:40:28 pm

it should be compiled with XFree86...

Well I could have built statically yes... But it was just making binaries bigger and eating more memory...
With all problems encountered by Linux users, I think that I will follow Rhad\'s advise and make a source package instead of pre-compiled binaries... especially since binaries must work on all Linux distribs...

Would you go for a source package?

In addition, people could easily make a binary package for their distribution from the source package....

Title:
Post by: uafr on April 15, 2003, 02:52:45 pm

Quote

Originally posted by Atanor
Would you go for a source package?

In addition, people could easily make a binary package for their distribution from the source package....

Sure, I would try that. Is there any difference between the code from source package and CVS?

Title:
Post by: Atanor on April 15, 2003, 02:59:50 pm

yes... CVS does not contain all the art/music files. In addition, CVS can contain unstable code...
Last, PS is using CS and CEL. So if CS/CEL devs change something in their projectn then incompatiblities could happen.

So the source package would include a snapshot of PS, CS, CEL and media files.
We will make scripts to make everything automated so that even newbies will be able to compile it...

So far it\'s the best sugegstion i got... Any comment ?

Title: libXxf86vm.so.1
Post by: Fluxen on April 15, 2003, 03:54:47 pm

Quote

What about a static version like 0.2.006?

.006 worked great for me too on Debian Sarge (except for the server not being .006 ;)

Quote

By the way: I checked the Package for  xwin.so. It is included,
but uses  
libXxf86vm.so.1 => not found

I found this on another board for that problem:

10.5 The program complains that it can\'t find \'libXF86VMode.so\'.
You probably only have the .a version. Here\'s a possible solution from http://www.home.mayn.de/comrad/?news=755 :
cd /usr/X11R6/lib
ar x libXxf86vm.a
g++ -shared -o libXxf86vm.so.1 XF86VMode.o
ln -s /usr/X11R6/lib/libXxf86vm.so.1 /usr/lib/libXxf86vm.so.1



Atanor, could I ask if it\'s difficult or dangerous to compile glibc2.3.2 on Debian? Do I need any patches to the standard GNU source? Or should I wait for a 2.3.1 based version?


Thanks

Title:
Post by: Atanor on April 15, 2003, 04:02:28 pm

Well it was a big hack i made... and it kinda broke all packages  :)  So I guess that you may wait...

But I am currently building a source package... that will allow everyone to build their own version of PS and say goodbye to such problems... expect a beta of this source package before the end of this week.

Title:
Post by: Fluxen on April 15, 2003, 04:21:27 pm

Excellent, thanks Atanor.

Title:
Post by: Sharaz on April 15, 2003, 05:45:49 pm

Thats\'t the best sollution, of course.
I\'ll try it the moment it comes out (and I have the time). :)

Title:
Post by: Isiliador on April 15, 2003, 08:37:41 pm

Quote

Originally posted by Fluxen
10.5 The program complains that it can\'t find \'libXF86VMode.so\'.
You probably only have the .a version. Here\'s a possible solution from http://www.home.mayn.de/comrad/?news=755 :
cd /usr/X11R6/lib
ar x libXxf86vm.a
g++ -shared -o libXxf86vm.so.1 XF86VMode.o
ln -s /usr/X11R6/lib/libXxf86vm.so.1 /usr/lib/libXxf86vm.so.1

Thanks alot Fluxen!

this fixed my probelem with the 0.2.010.tar.gz release

OS: Red Hat 9
standard packages that pertain to this except NVIDIA drivers

Title:
Post by: uafr on April 23, 2003, 05:54:01 pm

Quote

Originally posted by Atanor
But I am currently building a source package... that will allow everyone to build their own version of PS and say goodbye to such problems... expect a beta of this source package before the end of this week.

Where can I download the source package?

Title:
Post by: uafr on May 01, 2003, 08:39:41 pm

Okay, i got a new Version form CVS. It compiles and it is running.
I can play Planeshift with it. But it claims to be v0.2.008. Strange.

Title:
Post by: Atanor on May 02, 2003, 02:03:33 am

don\'t worry about the 008... it\'s okay.