I took a backup 16G SDHC card and made it a swap file.  The compile then 
proceeded farther.  Now the whole raspberry pi is locking up.  I don't get 
a response and the screen is suspended/saved.  I don't know if it crashes 
or if the processor is overloaded.  It just doesn't respond.  I ran it 
again and made a log.  The last few commands run were:

mv -f .deps/trsm.Tpo .deps/trsm.Plo
/bin/bash ./libtool  --tag=CC   --mode=compile gcc -std=gnu99 
-DHAVE_CONFIG_H -I. -I./m4rie   -I/home/pi/sage-5.5/local/include    
-I/include  -O2 -fPIC -Wall -pedantic -g  -I/home/pi/sage-5.5/local/include 
-MT ple.lo -MD -MP -MF .deps/ple.Tpo -c -o ple.lo `test -f 'm4rie/ple.c' || 
echo './'`m4rie/ple.c
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./m4rie 
-I/home/pi/sage-5.5/local/include -I/include -O2 -fPIC -Wall -pedantic -g 
-I/home/pi/sage-5.5/local/include -MT ple.lo -MD -MP -MF .deps/ple.Tpo -c 
m4rie/ple.c  -fPIC -DPIC -o .libs/ple.o
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./m4rie 
-I/home/pi/sage-5.5/local/include -I/include -O2 -fPIC -Wall -pedantic -g 
-I/home/pi/sage-5.5/local/include -MT ple.lo -MD -MP -MF .deps/ple.Tpo -c 
m4rie/ple.c -o ple.o >/dev/null 2>&1
mv -f .deps/ple.Tpo .deps/ple.Plo
/bin/bash ./libtool  --tag=CC   --mode=compile gcc -std=gnu99 
-DHAVE_CONFIG_H -I. -I./m4rie   -I/home/pi/sage-5.5/local/include    
-I/include  -O2 -fPIC -Wall -pedantic -g  -I/home/pi/sage-5.5/local/include 
-MT conversion.lo -MD -MP -MF .deps/conversion.Tpo -c -o conversion.lo 
`test -f 'm4rie/conversion.c' || echo './'`m4rie/conversion.c
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./m4rie 
-I/home/pi/sage-5.5/local/include -I/include -O2 -fPIC -Wall -pedantic -g 
-I/home/pi/sage-5.5/local/include -MT conversion.lo -MD -MP -MF 
.deps/conversion.Tpo -c m4rie/conversion.c  -fPIC -DPIC -o 
.libs/conversion.o

The last entry in the message log is:
Jan  1 01:34:58 raspberrypi kernel: [  535.890159] Adding 15182844k swap on 
/dev/sda1.  Priority:-2 extents:1 across:15182844k 
There is no kernel oops so maybe the raspberry pi is just busy/overloaded.  
I let it run for a few hours and it stayed locked up.

syslog has:
Jan  1 02:10:27 raspberrypi rtkit-daemon[3124]: The canary thread is 
apparently starving. Taking action.
Jan  1 02:10:27 raspberrypi rtkit-daemon[3124]: Demoting known real-time 
threads.
Jan  1 02:10:27 raspberrypi rtkit-daemon[3124]: Demoted 0 threads.
Jan  1 02:10:27 raspberrypi /USR/SBIN/CRON[7574]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ 
-depth -mindepth 1 -maxdepth 1 -type f -ignore_readdir_race -cmin 
+$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Jan  1 02:17:03 raspberrypi /USR/SBIN/CRON[7581]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
 I will try to check and see if other programs are crashing it.  I 
installed a lot of programs and some daemons are running that I don't want 
to.

Maybe rtkit-daemon is the problem. I found this link:
http://askubuntu.com/questions/48888/why-is-rtkit-daemon-eating-100-of-my-cpu
It is required by pulse-audio.

On Monday, December 31, 2012 3:46:48 PM UTC-6, Danny wrote:
>
>     A while back, I tried to compile on the Fedora distro for Raspberry Pi 
> and got similar messages. I was able to solve them by adding a swap file to 
> my system. The tiny amount of memory on the RasPi just can't seem to handle 
> it without a bit of help.
>     I also ran in to some other issues with ATLAS further on in the 
> compile. That was several months ago though, so they may have been fixed by 
> now.
>
>
> On Mon, Dec 31, 2012 at 11:33 AM, Don Harter <hart...@att.net<javascript:>
> > wrote:
>
>> I just got my raspberry pi and thought that I would try to build this.  
>> It crashes gcc.(not enough memory?)
>> Here is the log of what happened.  I had been building it for about 2 
>> days before the crash.
>> mv -f .deps/ple.Tpo .deps/ple.Plo
>> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -std=gnu99 
>> -DHAVE_CONFIG_H -I. -I./m4rie   -I/home/pi/sage-5.5/local/include    
>> -I/include  -O2 -fPIC -Wall -pedantic -g  -I/home/pi/sage-5.5/local/include 
>> -MT conversion.lo -MD -MP -MF .deps/conversion.Tpo -c -o conversion.lo 
>> `test -f 'm4rie/conversion.c' || echo './'`m4rie/conversion.c
>> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./m4rie 
>> -I/home/pi/sage-5.5/local/include -I/include -O2 -fPIC -Wall -pedantic -g 
>> -I/home/pi/sage-5.5/local/include -MT conversion.lo -MD -MP -MF 
>> .deps/conversion.Tpo -c m4rie/conversion.c  -fPIC -DPIC -o 
>> .libs/conversion.o
>> gcc: internal compiler error: Killed (program cc1)
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.
>> make[4]: *** [conversion.lo] Error 1
>> make[4]: Leaving directory 
>> `/home/pi/sage-5.5/spkg/build/libm4rie-20120613/src'
>> make[3]: *** [all-recursive] Error 1
>> make[3]: Leaving directory 
>> `/home/pi/sage-5.5/spkg/build/libm4rie-20120613/src'
>> Error building libm4rie
>>
>> real    22m48.683s
>> user    17m7.810s
>> sys    0m23.530s
>> ************************************************************************
>> Error installing package libm4rie-20120613
>> ************************************************************************
>> Please email sage-devel (http://groups.google.com/group/sage-devel)
>> explaining the problem and including the relevant part of the log file
>>   /home/pi/sage-5.5/spkg/logs/libm4rie-20120613.log
>> Describe your computer, operating system, etc.
>> If you want to try to fix the problem yourself, *don't* just cd to
>> /home/pi/sage-5.5/spkg/build/libm4rie-20120613 and type 'make' or 
>> whatever is appropriate.
>> Instead, the following commands setup all environment variables
>> correctly and load a subshell for you to debug the error:
>>   (cd '/home/pi/sage-5.5/spkg/build/libm4rie-20120613' && 
>> '/home/pi/sage-5.5/sage' -sh)
>> When you are done debugging, you can type "exit" to leave the subshell.
>> ************************************************************************
>> make[2]: *** [installed/libm4rie-20120613] Error 1
>> make[2]: Leaving directory `/home/pi/sage-5.5/spkg'
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory `/home/pi/sage-5.5/spkg'
>>
>> real    22m56.633s
>> user    17m10.100s
>> sys    0m24.220s
>> Error building Sage.
>> make: *** [build] Error 1
>> pi@raspberrypi ~/sage-5.5 $ 
>>
>> uname -a
>> Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 
>> armv6l GNU/Linux
>>
>> Raspbian “wheezy” If you’re just starting out, *this is the image we 
>> recommend you use*. It’s a reference root filesystem from Alex and Dom, 
>> based on the Raspbian <http://www.raspbian.org/> optimised version of 
>> Debian, and containing LXDE, Midori, development tools and example source 
>> code for multimedia functions
>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To post to this group, send email to sage-...@googlegroups.com<javascript:>
>> .
>> To unsubscribe from this group, send email to 
>> sage-devel+...@googlegroups.com <javascript:>.
>> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
>>  
>>  
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.


Reply via email to