Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Error compiling

Help
NeoReel
2007-03-29
2013-04-25
  • NeoReel
    NeoReel
    2007-03-29

    Hello all,

      Its the first time I'm trying to compile Pixie and I need a bit of help if thats possible.

      I'm using xubuntu command line (no graphic interface) to compile Pixie for my renderfarm (so without fltk, openexr, X11, etc.). The source gets configured allright, but when I get to use "make", the compilation gets interrupted after a while because the process gets out of memory. I compile on an Athlon 1.4ghz with 512mb of RAM, with GCC 4.1.1. Do you have any ideas why its doing this ?

      Thanks in advance,

    M-A

     
    • JasonBelec
      JasonBelec
      2007-03-29

      Yeah I had that awhile back. Probably going to have it again. Solved it by building a cross-compiler on FC5 on a Windows box. Not exactly elegant nor should it be necessary. About to try building this latest version for the farm as well. Use YDL on the farm, should be fun...

       
    • NeoReel
      NeoReel
      2007-03-30

      Hmmm.. I could not say I would know how to do that on either Fedora or Yellow Dog... Hmmm... Thanks for the toughts :-)

      Does anyone else has an idea about how to fix this ?

      Thanks!

      M-A

       
    • Nicholas Yue
      Nicholas Yue
      2007-03-30

      From my experience on OS X, there is one particular file which takes a long time to compile.

      I think on machine with lesser memory, the swap gets exhausted during the compilation

      http://sourceforge.net/forum/message.php?msg_id=2399953

       
    • JasonBelec
      JasonBelec
      2007-03-30

      Yeah we noticed this on the PPC YDL boxes as well as I mentioned above. Seems a little insane to require that much space all at once.

       
    • NeoReel
      NeoReel
      2007-03-30

      Hello again,

        Here is the tail of the log when I compile :

      ##################################################

      creating sdrc
      make[3]: Leaving directory `/usr/local/src/Pixie/src/sdrc'
      Making all in ri
      make[3]: Entering directory `/usr/local/src/Pixie/src/ri'
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Iutes.lo attributes.cpp; \         then mv -f ".deps/attributes.Tpo" ".deps/attributes.Plo"; else rm -f ".d
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT attributes.lo -MD -MP -MF .
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Io brickmap.cpp; \         then mv -f ".deps/brickmap.Tpo" ".deps/brickmap.Plo"; else rm -f ".deps/
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT brickmap.lo -MD -MP -MF .de
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Iundles.cpp; \         then mv -f ".deps/bundles.Tpo" ".deps/bundles.Plo"; else rm -f ".deps/bu
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT bundles.lo -MD -MP -MF .dep
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Ipp; \         then mv -f ".deps/cache.Tpo" ".deps/cache.Plo"; else rm -f ".deps/cache.
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT cache.lo -MD -MP -MF .deps/
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Ies.cpp; \         then mv -f ".deps/curves.Tpo" ".deps/curves.Plo"; else rm -f ".deps/curv
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT curves.lo -MD -MP -MF .deps
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I-c -o bsplinePatchgrid.lo bsplinePatchgrid.cpp; \         then mv -f ".deps/bsplinePatchgrid.Tpo" ".deps/bsplinePatchgrid.Plo"; el
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT bsplinePatchgrid.lo -MD -MPbsplinePatchgrid.o
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Ipp; \         then mv -f ".deps/debug.Tpo" ".deps/debug.Plo"; else rm -f ".deps/debug.
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT debug.lo -MD -MP -MF .deps/
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Ielayed.cpp; \         then mv -f ".deps/delayed.Tpo" ".deps/delayed.Plo"; else rm -f ".deps/de
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT delayed.lo -MD -MP -MF .dep
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Io dlobject.cpp; \         then mv -f ".deps/dlobject.Tpo" ".deps/dlobject.Plo"; else rm -f ".deps/
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT dlobject.lo -MD -MP -MF .de
      if /bin/bash ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../.. -Ixecute.cpp; \         then mv -f ".deps/execute.Tpo" ".deps/execute.Plo"; else rm -f ".deps/ex
      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT execute.lo -MD -MP -MF .dep
      g++: Internal error: Killed (program cc1plus)
      Please submit a full bug report.
      See <URL:http://gcc.gnu.org/bugs.html> for instructions.
      For Debian GNU/Linux specific bug reporting instructions, see
      <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.

      make[3]: *** [execute.lo] Error 1
      make[3]: Leaving directory `/usr/local/src/Pixie/src/ri'
      make[2]: *** [all-recursive] Error 1
      make[2]: Leaving directory `/usr/local/src/Pixie/src'
      make[1]: *** [all-recursive] Error 1
      make[1]: Leaving directory `/usr/local/src/Pixie'
      make: *** [all] Error 2

      ################################

      We are looking into inscreasing the swap space. Maybe that will fix the problem, but when I monitor the system ressources, I can clearly see the memory jumping from 30% usage to 94% usage.

      Thanks for any feedback.

      M-A

       
      • Bruce D'Amora
        Bruce D'Amora
        2008-05-04

        I also get internal error when compiling  specifically, execute.cpp. This is version 2.2.3 and ona quad-core intel system running FC/9 and with 2GB or memory. Anny suggestions on how to fix this?

         
        • Aasimon
          Aasimon
          2008-05-06

          If you watch your memory usage you will see it creeping up and up and up until it goes bang. :)
          I found on a Unbuntu x64 machine that giving it an extra 6 Gb of swap file space allowed it to compile. (This value might be over kill though)

          The other way around it is to try something like (I might have the syntax very wrong) to compile that one file with out optimizations.

          make execute.cpp FLAGS_CXX=O0

           
    • NeoReel
      NeoReel
      2007-04-02

      OK, I got it to work...

      My answer was here : http://www.george-graphics.co.uk/pixiewiki/FAQ/Why_Wont_Pixie_Run
      It just takes a LOT of time to compile.

      Regards,

      M-A

       
    • Vasi
      Vasi
      2008-07-13

      Hi all,
      I had same problems compiling Pixie under different Linux distributions, with different gcc versions. So, in Ubuntu 8.04 can be compiled only with gcc-3.4 compiler (very fast and without modification on original files - is about pixie 2.2.4 version). Install it and manually edit simlinks (@cpp, @g++, @gcc) with Midnight Commander to point to required version (default is 4.2 and must be 3.4).

      When all dependencies are ok (all required tools/libraries are in place) and you got very long compiling times and  ending with error, compiler version is the main problem. Always.

       
      • actualy you don't have to make symlinks. You may export environmen variables:
        CC=gcc
        CXX=g++

         
    • Vasi
      Vasi
      2008-07-13

      I forgot to mention, I compiled pixie 2.2.4 with gcc-3.4 under Ubuntu 8.04 for Linux PPC (Mac).