gentoo ebuilds for 0.3.018 is out :)

[loux]

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

[Jannis]

Emerging crystalspace-cs with USE="java" takes up more than 1GB of RAM on my system...... Dunno why

[sliss]

hmmm... 

Code: [Select]

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'



[Jannis]

Yep, same here

Code: [Select]

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'

[loux]

Jannis, sliss did you try to compile it with java flags ?
loux.thefuture

[Jannis]

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.

[loux]

ok don't compile crystalspace-ps and cel-ps with java flags !!!!
thanks
see you
loux.thefuture

[causality]

Loux, thank you for all of your feedback! 

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

With your help I think I now have all of this working correctly, but if I overlooked something please let me know. 

[loux]

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 ?

[causality]

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

[loux]

causality, you're welcome, but stay up, someone needs us, they have error in their compilation
loux

[Jannis]

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

[loux]

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

[morisori]

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 ?

[loux]

hello morisori,
mine are : 3ds alsa cal3d cg jpeg mng png sdl vorbis
loux