When trying to emerge pixie I ran into two problems: 1. execute.cpp is a huge file which caused me to run out of Virtual Memory (my spec 1G RAM 3G SWAP P4 2.8GHz, I don't think this is too shabby) and suggest we set the CXXFLAG to -O1 this worked better for me and I noticed others had had problems in the forums. Perhaps we should also set MAKEOPTS="-j1" as well? 2. Picked up a newer version from the website, I haven't implemented the previous patch for libcommon yet, if someone else want to feel free. I'm too concerned with getting things to work first. I patched it for a bug mentioned in their forums which causes the build to cut out shader.h. Anyone any opinions on this ebuild
Created attachment 100939 [details] pixie-1.7.6.ebuild New ebuild for Pixie
Created attachment 100941 [details, diff] pixie-1.7.6-shader.patch shader.h patch as suggested in the Pixie Forum on Sourceforge
(In reply to comment #2) > Created an attachment (id=100941) [edit] > pixie-1.7.6-shader.patch > > shader.h patch as suggested in the Pixie Forum on Sourceforge > Tganks for your efforts! Unfortunately I am still having trouble compiling this on my 1GB RAM system :( I used your ebuild/patch and made sure to comment my MAKEOPTS="-j2" line in /etc/make.conf but the compilation still runs out of memory and fails at: i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -O1 -MT execute.lo - MD -MP -MF .deps/execute.Tpo -c execute.cpp -fPIC -DPIC -o .libs/execute.o i686-pc-linux-gnu-g++: Internal error: Killed (program cc1plus) Please submit a full bug report. See <URL:http://bugs.gentoo.org/> for instructions. make[3]: *** [execute.lo] Error 1 make[3]: Leaving directory `/var/tmp/portage/media-gfx/pixie-1.7.6/work/Pixie/sr c/ri' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-gfx/pixie-1.7.6/work/Pixie/sr c' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-gfx/pixie-1.7.6/work/Pixie' make: *** [all] Error 2
How much swap have you got? When I build it compiling execute.cpp takesa about 20-30 min depending on what else I'm trying to do, and uses about 2.6G swap in addition to 70-80% of my ram. Hanni
(In reply to comment #4) > How much swap have you got? > > When I build it compiling execute.cpp takesa about 20-30 min depending on what > else I'm trying to do, and uses about 2.6G swap in addition to 70-80% of my > ram. > > Hanni > Ahh, well that explains it. I have a meager 512MB of swap space, not sure why I opted for such a small amount. I'll see if I can increase it and report back if I still run into problems.
Cool, well let me know, alternatively aqsis is renderman complient and on a par with pixie. > Ahh, well that explains it. I have a meager 512MB of swap space, not sure why I > opted for such a small amount. I'll see if I can increase it and report back if > I still run into problems. >
(In reply to comment #6) > Cool, well let me know, alternatively aqsis is renderman complient and on a par > with pixie. Yeah aqsis was actually the first renderer I tried (for use with K-3D), but the current stable version wouldn't compile with gcc4 (see bug # 115485) which led me to try pixie :) I did succeed at compiling the development snapshot of aqsis though the other day, so for now I'm good
virtual memory exhausted: Cannot allocate memory make[3]: *** [stochastic.lo] Błąd 1 make[3]: *** Oczekiwanie na niezakończone zadania.... i686-pc-linux-gnu-g++: Internal error: Killed (program cc1plus) Please submit a full bug report. See <URL:http://bugs.gentoo.org/> for instructions. make[3]: *** [execute.lo] Błąd 1 make[2]: *** [all-recursive] Błąd 1 make[1]: *** [all-recursive] Błąd 1 make: *** [all] Błąd 2 !!! ERROR: media-gfx/pixie-1.7.6 failed. :/ I had to turn off swap due to heavy disk usage, about 10 mb/s .After that I got error as above.
(In reply to comment #8) > virtual memory exhausted: Cannot allocate memory > make[3]: *** [stochastic.lo] Błąd 1 > make[3]: *** Oczekiwanie na niezakończone zadania.... > i686-pc-linux-gnu-g++: Internal error: Killed (program cc1plus) > Please submit a full bug report. > See <URL:http://bugs.gentoo.org/> for instructions. > make[3]: *** [execute.lo] Błąd 1 > make[2]: *** [all-recursive] Błąd 1 > make[1]: *** [all-recursive] Błąd 1 > make: *** [all] Błąd 2 > > !!! ERROR: media-gfx/pixie-1.7.6 failed. > > :/ I had to turn off swap due to heavy disk usage, about 10 mb/s .After that I > got error as above. > This program requires about 3.6 gig total available memory to compile execute.cpp, you have to use swap unless you have a very impressive machine. Hanni
Ok, setting jobs to -j1 and -O2 solved problem;)
2.0.1 was just released https://sourceforge.net/project/showfiles.php?group_id=59462 I've tried just modifying the ebuild, but it maxes out my CPU and uses all my ram in compiling and just sits there part way through. all changes in the patch on 1.6.3 are already in there except for -LIBCOMMON_CURRENT_VERSION=0 -LIBCOMMON_REVISION_VERSION=0 -LIBCOMMON_AGE_VERSION=0 +LIBPIXIECOMMON_CURRENT_VERSION=0 +LIBPIXIECOMMON_REVISION_VERSION=0 +LIBPIXIECOMMON_AGE_VERSION=0 i.e. all the libcommon has been changed to libpixiecommon Cheers, Alan.
(In reply to comment #11) > 2.0.1 was just released > https://sourceforge.net/project/showfiles.php?group_id=59462 > > I've tried just modifying the ebuild, but it maxes out my CPU and uses all my > ram in compiling and just sits there part way through. > > all changes in the patch on 1.6.3 are already in there except for > -LIBCOMMON_CURRENT_VERSION=0 > -LIBCOMMON_REVISION_VERSION=0 > -LIBCOMMON_AGE_VERSION=0 > +LIBPIXIECOMMON_CURRENT_VERSION=0 > +LIBPIXIECOMMON_REVISION_VERSION=0 > +LIBPIXIECOMMON_AGE_VERSION=0 > > i.e. all the libcommon has been changed to libpixiecommon > > Cheers, > > Alan. > Post your modified ebuild and I'll check it on my machine, the execute.cpp file - in the 1.7 version at any rate - takes about 30min of CPU time to compile (P4 2.8GHz) And used all my 1G ram and about 2.6G SWAP. Thanks for patching the libpixie too. Cheers, Hanni
Created attachment 110734 [details] Pixie 2.0.2 ebuild Hi, 2.0.2 has just come out - it supports 64bit officially now. I'm compiling at the moment - it all appears to be good so far. Thanks for the info on execute - it seems it was a lack of patience on my part. When compiled with -O0 it compiles very quickly - so there must be some serious optimization going on there. Will post again if I need to patch this to make it work, but it seems we're good for a pretty much straight install on the new releases. Cheers, Alan.
Just a quick note - 2.0.2 final compiled quickly here - even execute.lo took very little time on -O2 I also noticed pixie runs a lot faster compiled under O2 than O0. Cheers, Alan.
In CVS, thanks.
I've investigated this issue a bit, and I can't fully reproduce the problem. I do get much more memory consumption with gcc-4.1 over 3.4 and 4.0 when compiling pixie (1400M compared to 500M), but it's nowhere near the 2700M reported here. I have created a toolchain bug (bug #171367) with my findings, and I would greatly appreciate comments in that bug report from those of you who did experience this problem.
