Le dimanche 8 mai 2016 04:08:54 UTC+2, john_perry_usm a écrit :
>
> What about homogeneous cyclic-8? I'm not sure it will be any better; I'm
> just curious.
>
> I do know Singular is working on improving aspects of the sba()
> implementation, and I'm a bit surprised it's that slow.
>
That's i
On Sat, May 7, 2016 at 12:18 PM, Volker Braun wrote:
> You can set it yourself in the environment after moving Sage, this may work
> with the aforementioned caveats about conflicts with system libraries. And
> change SAGE_LOCAL/lib/sage-current-location.txt to avoid the relocation
> error message.
Hi,
I just tested this package for creating binaries. It creates by default a file
sage-7.2.rc1-Ubuntu_15.10-x86_64.tar.bz2
which is 593M.
Doing
time tar jxf sage-7.2.rc1-Ubuntu_15.10-x86_64.tar.bz2
takes just under 2 minutes (for me) and results in a directory
SageMath, rather than sag
On Monday, 2 May 2016 20:18:06 UTC-6, paulmasson wrote:
>
> Andrey, the test server is not completing evaluations. Just get the
> spinning GIF.
>
Turns out I've changed some logic when fixing Chrome and Firefox got
affected but not others. Now things work for me in Firefox and Chrome under
Lin
What about homogeneous cyclic-8? I'm not sure it will be any better; I'm
just curious.
I do know Singular is working on improving aspects of the sba()
implementation, and I'm a bit surprised it's that slow.
On Saturday, May 7, 2016 at 1:32:36 AM UTC-5, parisse wrote:
>
>
>
> Le samedi 7 mai 201
On Saturday, May 7, 2016 at 8:51:40 PM UTC+2, William wrote:
>
> My use case is building Sage on SageMathCloud (Ubuntu 15.10 right now)
> for people to develop on SageMathCloud (on the exact same machine).
Then just put sage in the same path for everyone (with a private union
mount), thats real
On Sat, May 7, 2016 at 11:32 AM, Volker Braun wrote:
> On Saturday, May 7, 2016 at 5:46:20 PM UTC+2, William wrote:
>>
>> I read that github page, but I don't know what binary-pkg actually
>> does.
>
>
> It compiles Sage in a long directory path.
>
>>
>> For context, I used to (1) build a copy of
On Saturday, May 7, 2016 at 5:46:20 PM UTC+2, William wrote:
>
> I read that github page, but I don't know what binary-pkg actually
> does.
It compiles Sage in a long directory path.
> For context, I used to (1) build a copy of Sage, (2) possibly
> customize it, then (3) type
>
> ./sage
On Sat, May 7, 2016 at 9:02 AM, Dima Pasechnik wrote:
> Yes, I know, I was puzzled by this some time ago too. The reason for all
> this mess is that in order to make
> a relocatable Sage binary (more precisely, a bunch of relocateable libs etc)
> that uses rpath, it has to be built at a location t
Yes, I know, I was puzzled by this some time ago too. The reason for all
this mess is that in order to make
a relocatable Sage binary (more precisely, a bunch of relocateable libs
etc) that uses rpath, it has to be built at a location that will allow
pattern-matching on binaries to work (so it h
On Sat, May 7, 2016 at 2:00 AM, Volker Braun wrote:
> The sage script in your PATH is outdated:
>
> $ ./sage -advanced | grep bdist
> $ egrep -r bdist src/
> $
>
> The way to build binary (relocatable) packages is
> https://github.com/sagemath/binary-pkg, which says:
>
> git clone https://github.c
11 matches
Mail list logo
