On 2016-02-22 23:18, Volker Braun wrote:
I think you just ran out of RAM
Most likely. Note the signal is "Killed", not "Segmentation Fault". So
it's probably the out-of-memory killer which killed your gcc.
--
You received this message because you are subscribed to the Google Groups
"sage-de
Thanks. I'll re-run it then, when I have the time.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group
I think you just ran out of RAM, you need about 2GB per CPU core to build
Sage. The gcc ice in scipy is a sign of running out of memory,
e.g. https://www.digitalocean.com/community/questions/cannot-install-scipy
On Monday, February 22, 2016 at 10:20:37 PM UTC+1, Martin Vahi wrote:
>
>
> Well,
I add that the VirtualBox virtual appliance had about 900MiB of RAM
allocated to it and it had about 90% of a single 3GHz CPU time allocated to
it, with the CPU supported accelerations.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscr
On Sunday, February 21, 2016 at 6:23:45 PM UTC, Martin Vahi wrote:
>
> I tried again. This time with the
>
> export SAGE_ATLAS_ARCH="base"
>
>
> added to the Bash script. I did not notice any differences at the log
> file, although I did not very thoroughly study it, because I'm not the
> m
On Sunday, February 21, 2016 at 5:01:35 PM UTC, Volker Braun wrote:
>
> On Sunday, February 21, 2016 at 11:07:48 AM UTC+1, Jeroen Demeyer wrote:
>>
>> One possible idea: the path
>> /home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/t
On Sunday, February 21, 2016 at 11:07:48 AM UTC+1, Jeroen Demeyer wrote:
>
> One possible idea: the path
> /home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0
>
>
> is unusually long, maybe try a shorter/simpler
On Sunday, February 21, 2016 at 10:07:48 AM UTC, Jeroen Demeyer wrote:
>
> On 2016-02-21 10:55, Martin Vahi wrote:
> > |gcc -fPIC
> >
> -L/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib
>
>
> >
On 2016-02-21 10:55, Martin Vahi wrote:
|gcc -fPIC
-L/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib
-Wl,-rpath,/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast
I tried to take the easy route, because I'm running out of time with my
project, but that also failed. The code and the bash script that I used for
building it resides (for review) at
(~600MiB, plain TAR file)
http://temporary.softf1.com/2016/2016_02_21_Sage_7_0_build_failure_demo.tar
This tim
The memcpy declaration is not picked up even though the configure test
found it, this seems more like a bug in glibc than the compiler. From the
log:
./string.h:276:5: warning: incompatible implicit declaration of built-in
function 'memcpy'
memcpy( libGAP_CHARS_STRING(string), (cstr), tmp_
In any case we need more info; Full logs, openSUSE version, glibc and
compiler versions, ...
On Saturday, February 6, 2016 at 11:51:43 PM UTC+1, Volker Braun wrote:
>
> The memcpy declaration is not picked up even though the configure test
> found it, this seems more like a bug in glibc than th
On 2016-02-04 18:50, Martin Vahi wrote:
The compilation of the Sage 7.0 was with LLVM, not GCC.
Are you sure? The log file says
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.8/lto-wrapper
Target: x86_64-suse-li
On Friday, 5 February 2016 19:34:47 UTC, Martin Vahi wrote:
>
>
>
> neljapäev, 4. veebruar 2016 20:30.12 UTC kirjutas Dima Pasechnik:
> ...
>
>> In a working build one will see
>> "checking whether we can use the existing Boehm-Weiser library ... yes"
>> rather than 'no'
>> ...
>>
>
> Thank You
Hi,
On Fri, Feb 05, 2016 at 11:34:47AM -0800, Martin Vahi wrote:
[...]
> Since I'm not a Sage developer, that concludes this bug report for me. I
> wonder, if it should be re-written to some bug-track or something
> similar? I've read that there's quite a specific procedure for filing
> those repo
neljapäev, 4. veebruar 2016 20:30.12 UTC kirjutas Dima Pasechnik:
...
> In a working build one will see
> "checking whether we can use the existing Boehm-Weiser library ... yes"
> rather than 'no'
> ...
>
Thank You for the answer. My interpretation of it is that the flaw within
the Sage is t
On Thursday, 4 February 2016 17:50:52 UTC, Martin Vahi wrote:
>
>
> I also tried to build the Sage 6.10. This time with the GCC.
> That failed to compile and the problematic
> package at the 6.10 compilation seems to be
>
> ecl-15.3.7p0
>
> The details reside at yet another set of attachment
Nobody ever built Sage with llvm, so you are in totally unchartered waters
here.
It would be interesting to know what goes wrong.
It's also a bit unclear how this would play together with gfortran (which
is part of gcc suite of compilers),
which is needed for a part of Sage.
HTH,
Dima
On Thurs
What is gcc installed on your system?
And how do you start the compilation?
(these things are not clear from your posts)
On Thursday, 4 February 2016 04:33:43 UTC, Martin Vahi wrote:
>
>
> The source was downloaded on 2016_02_04 from
>
> http://www.sagemath.org/download-source.html
>
> and the s
19 matches
Mail list logo
