PlaneShift
Support => Linux Specific Issues => Topic started by: loux on February 07, 2007, 09:36:33 am
-
Hello,
news :
2008-02-06: release ebuild : crystalspace-ps-1.1-r26294
2008-02-06: release ebuild ; cel-ps-1.1-r2592
2008-02-06: and planeshift-0.3.018
2008-02-07: fix digest on planeshift ebuild (thanks to causality)
2008-02-08: fix sandbox permissions on cel-ps ebuild (thanks to causality)
2008-02-08: fix USE trouble with java and CS/CEL (thanks to Jannis)
2008-02-09: channel on IRC : #planeshift-gentoo, i have a bot on it :)
2008-02-09: fix USE, ebuilds CS/CEL now don't use python/perl/java/wx and check for need depends
2008-02-09: warning : if you get "cannot open /config/gldrivers.xml" it's because i put a wrong CRYSTAL env ... change it to CRYSTAL=/opt/planeshift/crystalspace/lib/crystalspace in psclient.sh pssetup.sh and psupdater.sh :)
2008-02-14: fix remove compilation of .dbg files for cel
-------------------------------------------------------------------------------------------------
i just release new ebuilds for client 0.3.018 from 2007-02-07, crystalspace 26294 and cel 2592
a lots of change there, i advice you to unmerge planeshift, crystalspace and cel before merging new,
- ebuild of crystalspace and cel are now called crystalspace-ps and cel-ps because gentoo dev release officials ebuilds for crystalspace/cel which is NOT compatible with planeshift,
- don't worry my ebuilds are installed in /opt/planeshift/{crystalspace/cel} so they don't interfer with official ones,
- 3 scripts appears under /usr/games/bin : psupdater.sh, pssetup.sh and psclient.sh so you don't need to go in the good directory before launching it (it fixed the env too :)
see you soon
loux.thefuture
PS : take about change of ebuilds name in your portage.keywords or portage.unmask too
:oops: i realise that i didn't explain everything
Ok, create a overlay - mkdir /usr/local/portage & cd /usr/local/portage
download the ebuilds in it - wget http://loux.thefuture.free.fr/portage.tar.bz2
untar them - tar xjf portage.tar.bz2
add the overlay to gentoo echo "PORTDIR_OVERLAY=/usr/local/portage" >> /etc/make.conf
unmask them :
echo "dev-games/crystalspace-ps" >> /etc/portage/package.unmask
echo "dev-games/cel-ps" >> /etc/portage/package.unmask
echo "games-rpg/planeshift" >> /etc/portage/package.unmask
unkeywords them :
echo "dev-games/crystalspace-ps" >> /etc/portage/package.keywords
echo "dev-games/cel-ps" >> /etc/portage/package.keywords
echo "games-rpg/planeshift" >> /etc/portage/package.keywords
unuse them
echo "dev-games/crystalspace-ps -java" >> /etc/portage/package.use
echo "dev-games/cel-ps -java" >> /etc/portage/package.use
and compile : emerge planeshift
to have the new {art/data} folder, you need to download the binary and install it somewhere then copy {art/data} folder to /opt/planeshift/bin/.
-
I just wondered why the compiling-guide in CVS says:
PS CVS date: "2007-02-08 00:00:00 UTC"
Your post definitely the answer! Lookig forward to play 0.3.018 =D
(Is that why Laanx is wiped empty right now? Would be funny to be *alone* in Yliakum since the windows-builds aren't out yet)
-
Jannis,
so the emerge works ? you could launch psupdate.sh, pssetup.sh and finaly psclient.sh ?
loux
-
I'm just compiling the stuff without the ebuild manually to see the new features but be sure I'll test the ebuild after I've played 10 minutes. Unfortunately I've gotta go to work in 3 hrs, let's see if it's enough time or not.
-
What about submitting it to bugzilla?
moHiJ
-
HHmmm..... I can't even connect to Laanx with 0.3.018 :(
So, where can I find the ebuilds?
-
the server is down, for now, so it's normal to not be able to connect to server :)
loux
-
loux, can you give me some information about what is invovled with creating the ebuilds? I use Gentoo here myself but never did put in any research in how to create the ebuilds.
Thanks.
-
hello acraig, i was like few months ago,
to create a new ebuild i take one simple but working well and i adapt it for package i need, look at gentoo doc on ebuild :)
see you
loux
-
I am using the current ebuild from http://loux.thefuture.free.fr/portage.tar.bz2 and the latest version included therein is 0.3.017 (even though 0.3.018 is available at http://loux.thefuture.free.fr/distfiles). ;D I can't believe no one else noticed this. ;D Is there an alternative download site to get the 0.3.018 ebuild?
-
:oops: i'm so sorry to have forget to put new ebuilds on the site
causality points to me that
the trouble is repair now, i just upload the new portage.tar.bz2 with new ebuilds for all
see you
loux.thefuture
PS : one point for causality
-
Loux I followed your instructions but got a mask error after all:
localhost portage # emerge planeshift
Calculating dependencies
!!! All ebuilds that could satisfy "planeshift" have been masked.
!!! One of the following masked packages is required to complete your request:
- games-rpg/planeshift-0.3.017-r1 (masked by: package.mask)
# Philip Walls <malverian@gentoo.org> (18 Jul 2006)
# Package is a maintenance nightmare, it has depended
# on unreleased versions of several other packages
# for a very long time. This doesn't appear to be
# changing any time in the near future.
# Candidate for treecleaners
- games-rpg/planeshift-0.3.011 (masked by: package.mask, ~x86 keyword)
- games-rpg/planeshift-0.3.017-r3 (masked by: package.mask)
- games-rpg/planeshift-0.3.018 (masked by: package.mask)
- games-rpg/planeshift-0.3.017-r2 (masked by: package.mask)
For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
Whats your remark on this one?
-
Sliss,
It looks like you just need to unmask games-rpg/planeshift in /etc/portage/package.keywords and also in /etc/portage/package.unmask.
These two commands (as root) will add the needed entries:
echo "games-rpg/planeshift ~*" >> /etc/portage/package.keywords
echo "games-rpg/planeshift" >> /etc/portage/package.unmask
You may also end up having to do similar for some of Planeshift's dependencies, particularly since two of them (crystalspace and cel) now have the -ps suffix.
-
hello sliss, causality,
it's my fault : in the first post i write "game-rps" instead of "game-rpg", i repair the error,
thanks to have point that
see you
loux.thefuture
PS causality has 2 points now :)
-
I had an issue with the current ebuild for 0.3.0.018 in that the compile for cel-ps (ebuild file cel-ps-1.1-r2592.ebuild) would go smoothly and then the install would fail during the execution of the command "jam install" citing access violations (I am guessing it didn't deal well with being in a sandbox since this same command worked when done independently of Portage as the root user, but this is where I don't fully understand how emerge works). The "install" command was receiving permissions errors related to creating directories and files in /opt/planeshift/cel and no amount of adjusting the permissions of anything under /opt would remedy this problem.
Because the cel ebuild from your ebuilds for 0.3.0.017 (ebuild file cel-1.1-r2592.ebuild) didn't give me this problem, I modified the cel-ps-1.1-r2592.ebuild file to resemble the installation method used there, then rebuilt the "Manifest" file and again ran "emerge planeshift". Once I did this, cel-ps built and installed without a hitch on my system.
http://causality.ifastnet.com/psbuild/cel-ps-1.1-r2592.ebuild (http://causality.ifastnet.com/psbuild/cel-ps-1.1-r2592.ebuild) is my modified /usr/local/portage/dev-games/cel-ps/cel-ps-1.1-r2592.ebuild file.
If you replace/modify this file, then be sure to run this (as root) so that emerge won't fail due to mismatched checksums:
ebuild /usr/local/portage/dev-games/cel-ps/cel-ps-1.1-r2592.ebuild manifest
Also, once all dependencies were successfully built, the building of Planeshift itself failed because its Manifest (file /usr/local/portage/games-rpg/planeshift/Manifest) indicated an incorrect filesize for http://loux.thefuture.free.fr/distfiles/planeshift-0.3.018.tar.bz2 (http://loux.thefuture.free.fr/distfiles/planeshift-0.3.018.tar.bz2). To fix that, I edited the Manifest file and corrected the expected filesize. My modified file can be downloaded at http://causality.ifastnet.com/psbuild/Manifest (http://causality.ifastnet.com/psbuild/Manifest).
Once this was done, everything built with no problems and installed smoothly. The only possible "gotcha" was that after all the installation was done, the subsequent "etc-update" wanted to modify "/etc/cel/vfs.cfg" by adding two obviously incorrect entries that contained the /var/tmp/portage temporary working directory from the ebuild. I am not sure what caused this one, but it was easy to catch and the etc-update option of "2) Delete update, keeping original as is" took care of this.
For convenience, I also made a tarball of my /usr/local/portage overlay, which is loux's original work (from http://loux.thefuture.free.fr/portage.tar.bz2 (http://loux.thefuture.free.fr/portage.tar.bz2)) plus my modifications mentioned above. It's available at http://causality.ifastnet.com/psbuild/my_overlay.tar.bz2 (http://causality.ifastnet.com/psbuild/my_overlay.tar.bz2).
I am definitely no expert in Portage, so let me know if any of the above looks like a bad idea :D but the above changes made this work out for me.
-
hello causality,
thanks for all the remarks
- i have rebuild the manifest,
- i'm modyfing the ebuild of cel-ps with your advice
- your cel-ps ebuild is not good because you move things to main official cel ebuild place, so you delete them :( we place everything for ps in /opt/planeshift, but i'm making it
see you
loux.thefuture
-
Emerging crystalspace-cs with USE="java" takes up more than 1GB of RAM on my system...... Dunno why ;)
-
hmmm... ???
MkDir1 ./out/linuxx86/optimize/plugins/video/cursor
C++ ./out/linuxx86/optimize/plugins/video/cursor/cursor.o
LinkPlugin cscursor.so
ObjTagMetaData cscursor.so
...failed updating 1 target(s)...
...skipped 1 target(s)...
...updated 980 target(s)...
!!! ERROR: dev-games/crystalspace-ps-1.1-r26294 failed.
Call stack:
ebuild.sh, line 1546: Called dyn_compile
ebuild.sh, line 937: Called src_compile
crystalspace-ps-1.1-r26294.ebuild, line 72: Called die
!!! compile failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! This ebuild is from an overlay: '/usr/local/portage'
-
Yep, same here
C++ ./out/linuxx86/optimize/plugins/video/cursor/cursor.o
LinkPlugin cscursor.so
ObjTagMetaData cscursor.so
DoSplitDebugInfo cscursor.so
...failed updating 2 target(s)...
...skipped 2 target(s)...
...updated 987 target(s)...
!!! ERROR: dev-games/crystalspace-ps-1.1-r26294 failed.
Call stack:
ebuild.sh, line 1613: Called dyn_compile
ebuild.sh, line 970: Called qa_call 'src_compile'
environment, line 1242: Called src_compile
crystalspace-ps-1.1-r26294.ebuild, line 72: Called die
!!! compile failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/dev-games/crystalspace-ps-1.1-r26294/temp/build.log'.
!!! This ebuild is from an overlay: '/usr/local/portage'
-
Jannis, sliss did you try to compile it with java flags ?
loux.thefuture
-
Well, as I allready said:
Emerging crystalspace-cs with USE="java" takes up more than 1GB of RAM on my system...... Dunno why ;)
It wanted more and more RAM and when it had about 1,2GB I thought it was enough and killed it.
-
ok don't compile crystalspace-ps and cel-ps with java flags !!!!
thanks
see you
loux.thefuture
-
Loux, thank you for all of your feedback! \\o//
I corrected the ebuild cel-ps-1.1-r2592.ebuild so now everything is under /opt and I updated the file shown at http://causality.ifastnet.com/psbuild/cel-ps-1.1-r2592.ebuild (http://causality.ifastnet.com/psbuild/cel-ps-1.1-r2592.ebuild).
I also updated the tarball of the contents of my /usr/local/portage/ overlay, available at http://causality.ifastnet.com/psbuild/my_overlay.tar.bz2 (http://causality.ifastnet.com/psbuild/my_overlay.tar.bz2).
With your help I think I now have all of this working correctly, but if I overlooked something please let me know. 8)
-
causality,
why making another overlay for CS/CEL/PS ? one is not enough ?
see you
loux.thefuture
PS: i don't think it's a good idea because if something change, which one will be up to date ?
-
Loux,
This would be the first time I have ever tried to edit an ebuild or learn about how they work so my main reason for posting was to enjoy a "many-eyes" approach. I also decided it would be better for me to just "supply a patch" (or in this case, since the files are so small, I supply the ebuilds) in an attempt to be more constructive than just complaining that something doesn't work. I know I have made my files available on my Web site, but that should not be interpreted as meaning that I intend to become a package maintainer.
The question of which one people should be using is very easy to answer -- I don't intend to ever update the one I posted; that is a task better left to someone who knows more about this, such as you :D so naturally anyone else who just wants a working set of Planeshift ebuilds and is not interested in problems that seem to have now been solved should still be using your overlay at http://loux.thefuture.free.fr/portage.tar.bz2 (http://loux.thefuture.free.fr/portage.tar.bz2). I will be taking down the files on my Web site later today to avoid any confusion, since they seem to have served their purpose.
Thank you again for all of your feedback on this. With your help, I have learned much about how Portage works in only a couple of days. :thumbup:
-
causality, you're welcome, but stay up, someone needs us, they have error in their compilation :(
loux
-
loux, forget about the java-thingy, no one needs it to play PS (so you can throw away the use-flag and disable it by default. About the other error: CS is built correctly, it's just the ebuild which thinks the compilation has failed (can't look into it now since I'm at my girlfriend's with my laptop). So it's actually not a compilation- but an ebuild-related problem (maybe changed IF and ELSE-condition?)
-
Jannis,
you have post that :
<-
..failed updating X target(s)...
...skipped X target(s)...
->
so something goes wrong during the compilation time :(
and then the ebuild must stop
it would be very interesting to know which target don't compile :
cd /var/tmp/portage/the_name_of_ebuild/work/{cel or crystal or planeshift}/
nohup jam &
and cut/paste the nohup.out when its finished
thanks
loux.thefuture
PS : you'r right for the flag i will disable them java/perl/.. for the next release of my ebuilds
-
Hi thanks for the great work loux,
anyway, since i got a lot of flags enabled globally.. which are the use flags i NEED for cs/cel ? :)
-
hello morisori,
mine are : 3ds alsa cal3d cg jpeg mng png sdl vorbis
loux
-
And as soon as I used your useflags, my compilation errors vanished miraculously :)
-
great morisori,
i'm changing the ebuilds of crystalspace-ps/cel-ps to force and use only the flags needed by PS to work,
the emerge will stop if you don't have enough librairies like png, freetype2, ... and it will never use flags like python/perl/java/wx
so it will compile a lib just fine enough for PS and nothing more :)
see you
loux.thefuture
-
Why will the emerge stop? Just make them dependencies and they'll be installed automatically ;)
-
Jannis,
you're right, i think it will install dependencies before and not stop :)
see you
loux.thefuture
-
ok i think none of you got an amd64 or any other 64bit system to test the ebuilds.
there is an error while installing (like i already said to the chanbot(haven't read it right, so i talked to him))
if crystalspace is done you got those directories in /opt/planeshift/crystalspace:
drwxr-xr-x 2 root root 4096 Feb 13 20:33 bin
drwxr-xr-x 3 root root 4096 Feb 13 20:00 etc
drwxr-xr-x 3 root root 4096 Feb 13 20:00 include
drwxr-xr-x 3 root root 4096 Feb 13 20:00 lib64
drwxr-xr-x 4 root root 4096 Feb 13 20:00 share
so far so good, but the cs-config script is looking for the lib directory to get the --libs, --libdir,...
so you need to do a link to emerge cel as well
cd /opt/planeshift/crystalspace
ln -s lib64 lib
and you are ready to install cel.
-
SirTwist, thanks for you remarks about 64bit compilation,
should you say that during the installation process of CS i should make a symlink from /opt/planeshift/crystalspace/lib to /opt/planeshift/crystalspace/lib64 for amd64 ?
see you
loux
-
Loux, the compile went fine on my 64-bit box, except i had to set 2 symbolic links, since they were unresolved
cd /opt/planeshift/crystalspace
ln -s lib64/ lib
cd /opt/planeshift/cel
ln -s lib64/ lib
psclient.sh runs fine. The main problem i got now is i can't log in, since i had to run the updater which is unavailable now!
-----
a couple of minutes later:
since the updater is not available, i had to copy certain files from the bin version to get it to run
/data/options
/data/gui
/data/effects/spells
/art
optionally:
/data/zoneinfo.xml
/data/server.xml
since then it runs fine. I had a issue with starting some characters, i could login with one char, and with another could not log in. I was said, i know it sounds silly, anyway i was said "resize the fonts", and it worked.
;)