On Sunday, August 12, 2018 at 1:01:28 PM UTC-7, Jeroen Demeyer wrote:
>
> On 2018-08-12 17:39, vdelecroix wrote:
> > To construct the element x^-1 one has to use 1 // x because //
> > stands for "internal division" in Sage
>
> What does "internal division" mean? I would define // as Euclidean
On 8/12/18 4:01 PM, Jeroen Demeyer wrote:
On 2018-08-12 17:39, vdelecroix wrote:
To construct the element x^-1 one has to use 1 // x because //
stands for "internal division" in Sage
What does "internal division" mean?
Division of a by b means the element c so that a = b * c. Of
course, b
Dear all -
Just for the record, I started using flipper in sage and immediately got
bitten by this. I'll vote for ~n meaning some version of bit flipping
(preferably python's).
best,
saul
On Monday, June 6, 2016 at 6:13:19 AM UTC-4, Jeroen Demeyer wrote:
>
> On 2016-06-06 10:39, Erik
On 2018-08-12 17:39, vdelecroix wrote:
To construct the element x^-1 one has to use 1 // x because //
stands for "internal division" in Sage
What does "internal division" mean? I would define // as Euclidean
division (in some unspecified way since Euclidean division is not
unique). So I
On 2018-08-12 17:39, vdelecroix wrote:
From the answers to that thread, it seems that rule
(R0) The parent of a / b should only depend on the parents
of a and b.
has to be strict (7 people for and 2 vaguely against). The two
main reasons are consistency accross the different Sage
>From the answers to that thread, it seems that rule
(R0) The parent of a / b should only depend on the parents
of a and b.
has to be strict (7 people for and 2 vaguely against). The two
main reasons are consistency accross the different Sage rings
and the fact that coercion relies
I have two versions od sage on my Ubuntu 18-0 machine, both compiled
from source (git downloaded).No problem
I obtain
SageMath version 8.3, Release Date: 2018-08-03
with the first one
SageMath version 8.4.beta0, Release Date: 2018-08-05
>which sage
/usr/local/bin/sage
>ls -l /usr/local/bin/sage
Try
MAKE="make -j1" make
to not build stuff in parallel.
On Sunday, August 12, 2018 at 2:42:14 PM UTC+2, Will Sinclair wrote:
>
> Ok, so I have installed the gfortran manually. And I have re-run the make
> command. Now, it is the fplll that is giving me problems. (see log
> attached) I am
you are using gcc 4.8.5, which is quite old.
Probably fplll is not tested with it.
It might also be that you need a bigger swap. Normally swap should be as big as
your available RAM.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
Ok, so I have installed the gfortran manually. And I have re-run the make
command. Now, it is the fplll that is giving me problems. (see log
attached) I am not sure how to deal with the error 'virtual memory
exhausted' I have 512MB of swap and 4 G of ram. I am not quite sure how to
proceed
On
That’s fine. redhat’s naming scheme can be confusing, especially if you come
from
another distro.
François
> On 12/08/2018, at 21:34, Will Sinclair wrote:
>
> I tried the command yum install gfortran, but however it required root, so I
> tried it with root access, but ended up with "no
I tried the command yum install gfortran, but however it required root, so
I tried it with root access, but ended up with "no package
gfortran available". I dug around and installed gcc-gfortran? I am not sure
if it is the same thing. I just can't seem to find gfortran-7.2.0
On Sunday, August
it might be easiest to install the system package gfortran. (yum install
gfortran).
Then Sage would be using it rather than building one.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
13 matches
Mail list logo
