On Monday, August 20, 2018 at 8:44:48 AM UTC+10, Travis Scrimshaw wrote:
>
> Hi Julian,
>
> On Saturday, August 18, 2018 at 5:59:55 AM UTC+2, Travis Scrimshaw wrote:
>>>
>>> Thank you for working towards giving us extra tools to help us prevent
>>> regressions. It is definitely something we can
Hi Julian,
On Saturday, August 18, 2018 at 5:59:55 AM UTC+2, Travis Scrimshaw wrote:
>>
>> Thank you for working towards giving us extra tools to help us prevent
>> regressions. It is definitely something we can put to good use. However,
>> the total time it takes to test a file is somewhat of a
could you post the precise type of your CPU?
could you do
SAGE_CHECK=yes ./sage -f mpir
and report the result?
--
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 s
Is sage not included in ubuntus repos? Alternatively if it is a hardware
detection problem you could try building with SAGE_FAT_BINARY=1 or, as a
bit of self promotion, install sage through nix.
Am Sonntag, 19. August 2018 20:06:55 UTC+2 schrieb Mathieu Roux:
>
> aie aie aie
>
> but i have just
aie aie aie
but i have just installed my new linux, after formating hard disk... I
took last version of linux mint cinnamon.
What can i do? Is there a new solution but building sage from sources?
Le 19/08/2018 à 19:53, Dima Pasechnik a écrit :
system's ecl is not used by Sage, so this is n
system's ecl is not used by Sage, so this is not relevant whether it is
installed by apt, or not.
but segfault at the end of ecl's log is not nice at all. Something is broken in
the toolchain, the hardware is not recognised correctly...
--
You received this message because you are subscribed t
it is a mystery without the log of the ecl build, again, in logs/pkgs/
Do post it.
--
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...@googlegro
I do ./configure, and then make, and i get:
[ecl-16.1.2.p5] Makefile:75: recipe for target 'bin/ecl' failed
[ecl-16.1.2.p5] make[5]: *** [bin/ecl] Error 139
[ecl-16.1.2.p5] make[5]: Leaving directory
'/home/m/Bureau/sage-8.3/local/var/tmp/sage/build/ecl-16.1.2.p5/src/build'
[ecl-16.1.2.p5] Makefil
On Sunday, August 19, 2018 at 12:02:36 PM UTC+3, Mathieu Roux wrote:
>
> Here is the file gfortran-7.2.0.log.
>
../../../src/libgcc/libgcc2.c: In function '__mulxc3':
../../../src/libgcc/libgcc2.c:1998:6: internal compiler error: Illegal
instruction
a = COPYSIGN (isinf (a) ? 1 : 0, a);
On Sunday, August 19, 2018 at 12:38:10 PM UTC+3, Mathieu Roux wrote:
>
> So...
>
> I have just launched
>
>sudo apt-get install gfortran
>
> and there was no problem.
>
at this point you do not need building Sage's gfortran any more.
Could you try running
./configure
(which will output a lo
So...
I have just launched
sudo apt-get install gfortran
and there was no problem.
And then, i launched
make
again for Sage.
Same problem...;
[gfortran-7.2.0] ../../../src/libgcc/libgcc2.c: In function '__mulxc3':
[gfortran-7.2.0] ../../../src/libgcc/libgcc2.c:1998:6: inte
Hi Travis,
I am not sure I understand what you are observing.
On Saturday, August 18, 2018 at 5:59:55 AM UTC+2, Travis Scrimshaw wrote:
>
> Thank you for working towards giving us extra tools to help us prevent
> regressions. It is definitely something we can put to good use. However,
> the tot
12 matches
Mail list logo
