PlaneShift
Support => Technical Help: Problems BEFORE entering the game => Topic started by: Sharaz on June 10, 2003, 12:44:17 pm
-
Before everybody starts....
Yes I know there\'s a MB under Linux thread in this forum, but it\'s getting so polluted it\'s almost impossible to keep a sane thread.
So I did the evil thing and started this new one...;(
After a bit of trouble (my version of Sid uses g++/gcc3.3, so I had to use some configure options to use 2.95) I managed to compile everything.
CS: Walktest works
CEL: celtest works
PS: psclient gives the following error:
crystalspace.font.freefont2: Could not open fontfile /fonts/ttf/arial.ttf!
loading definitions file /planeshift/gui/psgui.def...
load successful (0 windows, 1 skins loaded.)
aws-debug: setting up global AWS palette...
aws-debug: finished palette setup.
planeshift.application.client: No iDialogManager plugin!
planeshift.application.client: Failed to init app!
Please anybody, how do I fix this. I\'ve been trying to get PS to run ever since MB came out. :-(
Ow yeah, I used the \'Building from CVS in Linux\' guide by Acraig
-
This looks like the dialogplugin was not built in PlaneShift. You can try to:
jam -aq psgui
( that should try to rebuild it and then quit on the first error it sees. )
-
jam -aq psgui
I tried this and it compiled without any errors....
But the problem still remained.
Any other possibilities?
-
*bump*
Any devs or other Linux users have any ideas?
-
Sharaz, I doubt that this is the full listing of all error messages. Did it complain about psgui.so ? Did you try to run it with -verbose option ?
-
OK, this is the full listing of psclient -verbose
*edit: Fixed the missing csjngimg *
Warning: Failed to load `psgui\'; reason(s):
DLERROR (psgui): ./psgui.so: undefined symbol: GetPlLayer__7CelBase
Warning: Failed to load `psgui\'; reason(s):
DLERROR (psgui): ./psgui.so: undefined symbol: GetPlLayer__7CelBase
WARNING: could not load plugin \'planeshift.gui.dialogmanager\'
Warning: Failed to load `psadmin\'; reason(s):
DLERROR (psadmin): ./psadmin.so: undefined symbol: GetMainActor__11psCelClient
Warning: Failed to load `psadmin\'; reason(s):
DLERROR (psadmin): ./psadmin.so: undefined symbol: GetMainActor__11psCelClient
WARNING: could not load plugin \'planeshift.admin.adminmanager\'
block_size: 8192
Mounting maps: podium.
planeshift.application.client: Planeshift Molecular Blue
planeshift.application.client: This game uses Crystal Space Engine created by Jorrit and others
planeshift.application.client: 0.97 rdev [Unix-x86-GCC]
crystalspace.font.freefont2: Could not open fontfile /fonts/ttf/arial.ttf!
loading definitions file /planeshift/gui/psgui.def...
load successful (0 windows, 1 skins loaded.)
aws-debug: setting up global AWS palette...
aws-debug: finished palette setup.
planeshift.application.client: No iDialogManager plugin!
planeshift.application.client: Failed to init app!
-
Originally posted by Sharaz
Warning: Failed to load `psgui\'; reason(s):
DLERROR (psgui): ./psgui.so: undefined symbol: GetPlLayer__7CelBase
Warning: Failed to load `psgui\'; reason(s):
DLERROR (psgui): ./psgui.so: undefined symbol: GetPlLayer__7CelBase
WARNING: could not load plugin \'planeshift.gui.dialogmanager\'
Warning: Failed to load `psadmin\'; reason(s):
DLERROR (psadmin): ./psadmin.so: undefined symbol: GetMainActor__11psCelClient
Warning: Failed to load `psadmin\'; reason(s):
DLERROR (psadmin): ./psadmin.so: undefined symbol: GetMainActor__11psCelClient
WARNING: could not load plugin
I run Debian Woody and I got the same errors. IMHO the compilation of psgui.so just does not work under Debian. I was trying to fix this but I ended up fighting with this weird \"jam\" thing.
-
Ok, that makes (at least) 2 Debian users with the same problem.
Please devs, any ideas?
-
Come on everybody, doesn\'t anyone have a clue on how to help us?!?
I searched the entire forum, found one real reference, tried that sollution (compile CS, copy cs-config to CEL, compile CEL, compile PS) and it still doesn\'t work.
I really want to play PS, but this is getting real depressing. :(
-
What version of PS are you trying to build? What -r tag did you use when you cvs checkout\'d everything?
-
-rMB010
-
I followed acraig\' s CVS building for Linux guide, just like scrythe. So yes, -rMB010
-
*bump*
Come on people, I\'ve been trying to get in since the release of MB!
Please help. :-(
-
I built from the source tarball, that seems to work fine, except HW redrering, but i suspect my drivers are the source of that problem. On Debian SID that is.
Haven\'t tried the guide\'s way of building it.
-
Sharaz, it just doesn\'t look like it was built successfully.
If it can\'t find the .so files, that means your make or jam didn\'t work. Paste in those errors and we\'ll try to help.
-
Vengeance, it did find the .so files, but it did not find some symbols in them.
I just tried to use gcc-3.2 instead of gcc-2.95.4 at it seems some of the problems are away.
-
Regarding the crash - there is a bug in
void *csSCF::CreateInstance (const char *iClassID, const char *iInterface, int iVersion)
in file CS/libs/csutil/scf.cpp
here:
instance = object->QueryInterface (GetInterfaceID (iInterface), iVersion);
object->DecRef ();
\'instance\' is not checked for NULL
(my assert says \"Assertion `instance!=__null\' failed.\")
In my case \'instance\' is null when calling with these arguments:
iClassID = \"iCelPlLayer\"
iInterface = \"4\"
iVersion = 1
-
It\'s running ! :)) This worked for me: install gcc-3.2 and make it default compiler (i symlinked gcc-3.2 and g++-3.2 as \"gcc\" and \"g++\" to /bin). Then run jam clean in all directories: CS, cel and planeshift. Then jam it all. If \"LinkApplication psclient\" complains about unresolved references then remove ps/out/linuxx86/pscomp.o and run jam again (because now the right pscomp.cpp will get compiled instead of the wrong pscomp.cpp - there are two with same name). Now you are nearly done :) It still crashes on world initialization screen though.
-
Awww ..... forget my silly bug report, there _is_ a check :-/
-
YESSSSS, it works for me too!
You don\'t even have to make 3.2 your default compiler, adding:
CC=gcc-3.2 CXX=g++-3.2 CPP=cpp-3.2
to each \'./configure ......\' line does the trick.
Thanks scrythe for finding the sollution. :)