Author Topic: An adventure in install!  (Read 1201 times)

sansavarous

  • Wayfarer
  • *
  • Posts: 1
    • View Profile
An adventure in install!
« on: December 09, 2005, 06:19:04 am »
Having grown disgusted with the pay for play existing MMORPG, or should I say MMOG (Massively Multiplayer Online Grind) I went exploring.

I found several intresting MMO games, then I stumbled across PlaneShift. This intrested me. Here is a growth of what I loved in the old MU* games. Open code, friendly people, and Role Play! Yes Role Play something almost totaly lacking in the pay for play market.

So I decided to investigate and install. I run Gentoo GNU/Linux. I have for several years. I understand about compiling and configuring source. Now I am no programmer, I consider myself to be a pretty good systems engineer/admin. So most issues, installs, configs and requirements I can handle in alpha and pre-alpha software.

I decided it would be best to start with the gentoo packages. So I did the emerge planeshift. That was painless, as most gentoo emerges are. Then I tried to update, bummer updater out of date. No biggie I\'ll hit the forums. Yep right here the fix, ok downloaded got the updater. Ran the updater, waited, and waited, nice it\'s done. Ran the config, great all goes well. Ran the client, wait what\'s this... a missing library, no problem emerge the lib. Then ran the client again, it said something about lighting and to use a certan flag. Ok did that, then ran the client again.

Much to my chigrin the dreaded Segmentation Fault.

Cripes, what now.... did I miss a step, is somthing missing, where do I start troubelshooting this...

I read over the forums and the planeshift site. And the community spoke to me is a voice whispering over my sholder, \"Use the source\".

Sweet, yeah I did CVS with Enlightenment, I can do that. So now I\'m CVSing down the source and compiling it. I\'ll edit this post later with info on how it goes.

DISCLAIMER: I am not an english majr, if I could spell I would be a wrigter. All opinions are my own, if you don\'t like \'em send mail to dev@null.com

For those that don\'t know MU* stands for MUSH, MUD, MOO and many other text adventure games that predate the graphical MMO\'s. Ask uncle google about mud.

*EDIT 12/9/05*

Well the jam compiles went off without a hitch. I followed the directions on the CVS page and they were very comprehensive. Started the update and got some sleep. This morning I ran the setup program and made sure it fit with my system and the options I wanted.

Then the moment of truth, I ran psclient and YIPPIEEEE!

Awww bummer not many models for the characters yet, no customisation. Oh well it\'s alpha, it\'s to be expected, did some exploring and talking to others. Too bad I\'m off to work, I\'ll play more Saturday!

See you online!
« Last Edit: December 09, 2005, 04:46:26 pm by sansavarous »

Bereror

  • Hydlaa Notable
  • *
  • Posts: 773
    • View Profile
    • Planeshift API
(No subject)
« Reply #1 on: December 09, 2005, 06:39:05 am »
Gentoo ebuild is broken and not updated. Either use the Xordan\'s installer or build your own from CSV. A hint from another Gentoo user: emerge -C cel cal3d crystalspace to avoid conflicts with the ones that are included in Xordan\'s installer or built from CVS.
PlaneShift Sources
PlaneShift API
"Words never spoken
Are the strongest resounding"

DaNIsH

  • Wayfarer
  • *
  • Posts: 1
    • View Profile
(No subject)
« Reply #2 on: December 10, 2005, 04:02:17 am »
I\'m in the same situation, except I get a \"Segmentation Fault\" when trying to select a character race :(
EDIT: Better point out, this is using CVS.
« Last Edit: December 10, 2005, 04:05:43 am by DaNIsH »

Tharizdun

  • Hydlaa Resident
  • *
  • Posts: 168
    • View Profile
(No subject)
« Reply #3 on: December 12, 2005, 05:06:32 am »
Crystalspace-CVS has also been uncompilable on Gentoo/x86\'s gcc ( 3.3.x series ) since about May this year, too many bits of it were broken and the CS developers must have migrated to a new compiler toolchain and inadvertently broken compatibility with older gcc\'s along the way.

Happily, that has all changed now that gcc 3.4.x has been flagged stable in x86 world, crystalspace and the other planeshift bits can compile now. amd64 arch on the other hand has has 3.4.x marked as stable for a long time, so those of you with opteron/athlon64 rigs have not missed out on anything.. its a terrible thing to have to choose between planeshift and running a compiler ( and hence a system ) that is not yet deemed to be stable..

I\'ve nearly finished my updater run, I\'m dying to see what has changed and been improved on in the last 6 months!

Xordan

  • Crystal Space Developer
  • Forum Addict
  • *
  • Posts: 3845
  • For God and the Empire
    • View Profile
(No subject)
« Reply #4 on: December 12, 2005, 12:34:49 pm »
Quote
Originally posted by Tharizdun
its a terrible thing to have to choose between planeshift and running a compiler ( and hence a system ) that is not yet deemed to be stable.


I should point out that it\'s perfectly safe to run a ~x86 or ~amd64 system. I\'ve never had a stability problem with it anyway. If you only use x86/amd64 packages then you\'ll have a rock solid bug-free system, but a bit of an old system, and you\'ll miss out on a lot of nice features for quite some time. :)

Tharizdun

  • Hydlaa Resident
  • *
  • Posts: 168
    • View Profile
(No subject)
« Reply #5 on: December 13, 2005, 02:19:00 pm »
Quote
Originally posted by Xordan

I should point out that it\'s perfectly safe to run a ~x86 or ~amd64 system. I\'ve never had a stability problem with it anyway. If you only use x86/amd64 packages then you\'ll have a rock solid bug-free system, but a bit of an old system, and you\'ll miss out on a lot of nice features for quite some time. :)


Yeah yeah, ~x86 is all the rage for those wanting to tinker and use the latest shiniest gcc flags ( assuming they arent one of these crazy people that have moved on to 4.x already ), but a compiler version bump affects a whole pile of issues that arent confined to just the compiler, otherwise I would just use /etc/portage/package.keywords to pick ~x86 for it. I guess I could have installed 3.3.x and 3.4.x together and used the config tool to pick 3.4.x for planeshift and set default back to 3.3.x when done compiling, but thats opening up a can of worms.. dont know how well it would interoperate with SDL, OpenAL, etc that were all compiled with the different C++ ABI of the 3.3.x gcc branch.

But thats ancient history now.

Bereror

  • Hydlaa Notable
  • *
  • Posts: 773
    • View Profile
    • Planeshift API
(No subject)
« Reply #6 on: December 13, 2005, 04:22:11 pm »
I guess you all already know that gcc 3.4.4 was marked stable on December 5th? Second day going here and still 273 packages to compile, so no Planeshift for another day  :(
PlaneShift Sources
PlaneShift API
"Words never spoken
Are the strongest resounding"