Wow, we crashed GCC:

libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I./m4rie -
I/opt/sage/sage-5.4.rc3/local/include -I/include -mmmx -msse -msse2 -msse3 -O2 
-fPIC -Wall -pedantic -g -I/opt/sage/sage-5.4.rc3/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/trsm.Tpo .deps/trsm.Plo
mv -f .deps/ple.Tpo .deps/ple.Plo
gcc: internal compiler error: Killed (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.

But I have no idea how to fix it (other than perhaps - as that thread you link 
to indicates - involve reinstalling GCC) 

On Sunday 04 Nov 2012, Brandon Curtis wrote:
> I am attempting to build Sage on a Linode-hosted [1] Linux virtual server.
>  Both sage-5.3 and sage-5.4-rc3 fail repeatedly at libm4rie-20120613.
> 
> I found one other reference to a similar problem [2], but reinstalling
> buildessential did not help.  I have gcc-4.6, but I have also tried with
> gcc-4.5 and gcc-4.4 (using export CXX="gcc-4.N") without success.
> 
> libm4rie-20120613.log - http://pastebin.com/9sJM8Fg8
> 
> [1] http://www.linode.com/
> [2]
> https://groups.google.com/forum/?fromgroups=#!topic/sage-support/PMtuoWdpcJ
> 0
> 
> Thoughts or suggestions?
> 
> *
>   Brandon Curtis, PhD Candidate
> UC Berkeley - Chem/Bio Eng <http://www.linkedin.com/in/brandoncurtis>
> <https://kindle.amazon.com/profile/Brandon-Curtis/5046185>
>   <https://plus.google.com/u/0/105858766264293200612/about>
> <http://brandoncurtis.net>
>   <http://jbei.org>
> *

Cheers,
Martin

--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://martinralbrecht.wordpress.com/
_jab: [email protected]

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


Reply via email to