Re: Problem compiling BrCreationId

From: Christian Holm Christensen (cholm@hehi03.nbi.dk)
Date: Wed Jul 18 2001 - 05:35:28 EDT

  • Next message: Christian Holm Christensen: "Re: problems compiling brat 2.0.9"

    Hi Kris, 
    
    On Tue, 17 Jul 2001 18:20:43 -0500
    Kris Hagel <hagel@comp.tamu.edu> wrote
    concerning ": Problem compiling BrCreationId":
    > Hello,
    > I tried for the first time since my vacation to download a fresh version
    > of brat and the build (using ./autogen
    > --prefix=/home/hagel/brat_cvs/brat) failed on BrCreationId saying
    > virtual memory exhausted.  It is the machine here at TAMU that has
    > compiled brat thousands of times.
    
    "virtual memory exhausted" usually means that both your swap and real
    memory (RAM) are all used up, and the kernel cannot allocate new
    pages.  I can imagine a number of things that may make that happen: 
    
    * You're running an obscene number of programs taking up all the
      memory (some one could have started shity programs like Mathematica,
      Netscape, Star Office, etc, many many times over).
    * You're machine has very little memory, below 32 MB RAM and 64 MB
      swap space. 
    * You have a buggy kernel
    * You have a buggy compiler
    
    The reason you may not have seen this with BRAT 1, could be that we
    now turn on optimisation (level 2 per default), which obviously make
    the compiler need more time/memory.  You may all have noticed that
    BRAT now takes a little longer to build - optimisation is the reason. 
    
    > Any ideas from anyone?
    
    Possible remedies: 
    
    * Kill all shity programs, uninstall them, and spank any user that
      wants them. 
    * Buy more RAM (It's comparible cheap at the moment, ~120 US$ for
      256MB) 
    * Allocate more swap space.  You don't need to repartiion you harddisk
      to do that.  Any superuser (root) can make a file and add that as
      swap space (see man swapon). 
    * Install a new compiler (_not_ GCC 2.96-Redhat, but GCC 2.95.3)
    * Try another machine. 
    * Try bootig up in single user mode and compile there (just to test a
      theory of mine :-)
    
    > I am using g++ 2.91.66.
    
    I'd really like to know a bit more details.  The output of  
      
      uname -a
    
    would help a lot, and the first three lines of 
    
      cat /proc/meminfo 
    
    when your compilation failed (actually just before) would also be
    nice. 
    
    Yours, 
    
    Christian  -----------------------------------------------------------
    Holm Christensen                             Phone:  (+45) 35 35 96 91 
      Sankt Hansgade 23, 1. th.                  Office: (+45) 353  25 305 
      DK-2200 Copenhagen N                       Web:    www.nbi.dk/~cholm    
      Denmark                                    Email:       cholm@nbi.dk
    
        
        
    



    This archive was generated by hypermail 2b30 : Wed Jul 18 2001 - 05:36:34 EDT