In spkg-install you need to add a suitable branch in configure_base():
On Monday, February 23, 2015 at 11:36:42 AM UTC+1, Snark wrote:
Hi,
Le 21/02/2015 17:25, Volker Braun a écrit :
The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing
else
to see here.
I
Hi,
Le 21/02/2015 17:25, Volker Braun a écrit :
The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing else
to see here.
I compiled sage-6.5 with my usual setup, then tried:
export SAGE_FAT_BINARY=yes
./sage -f atlas
and the compilation with :
Traceback (most recent call
Le 23/02/2015 15:05, Julien Puydt a écrit :
Le 23/02/2015 14:27, Julien Puydt a écrit :
That will take some time though : this box isn't fast. And I work on it
while it plays with sage.
In fact, when an arch is given, it does compile ad nauseum so it doesn't
take that much time.
The box
The base configuration is supposed to be a fixed one. If you want to tune
for your respective cpu then we can do that already.
On Monday, February 23, 2015 at 3:26:47 PM UTC+1, Snark wrote:
Le 23/02/2015 15:05, Julien Puydt a écrit :
Le 23/02/2015 14:27, Julien Puydt a écrit :
That will
Hi,
Le 23/02/2015 12:13, Volker Braun a écrit :
In spkg-install you need to add a suitable branch in configure_base():
Yes, but my question was : how do I know how to write that branch? I
didn't manage to get from configuration import conf to work, so I
couldn't look at 'conf' to know what
On 2015-02-23, Julien Puydt julien.pu...@laposte.net wrote:
Le 23/02/2015 15:05, Julien Puydt a écrit :
Le 23/02/2015 14:27, Julien Puydt a écrit :
That will take some time though : this box isn't fast. And I work on it
while it plays with sage.
In fact, when an arch is given, it does
On Monday, February 23, 2015 at 3:34:08 PM UTC+1, Dima Pasechnik wrote:
On 2015-02-23, Julien Puydt julien...@laposte.net javascript: wrote:
Le 23/02/2015 15:05, Julien Puydt a écrit :
Le 23/02/2015 14:27, Julien Puydt a écrit :
That will take some time though : this box isn't fast.
Le 23/02/2015 15:34, Volker Braun a écrit :
The base configuration is supposed to be a fixed one. If you want to tune
for your respective cpu then we can do that already.
What do we fix to, then armv7 or armv6 ?
Snark on #sagemath
--
You received this message because you are subscribed to
Le 23/02/2015 15:33, Dima Pasechnik a écrit :
hmm, shouldn't there also be a distinction between hardware and software
floats?
(Although I believe ARM chips you want to run Sage on all have hardware
floats - but the question is how the OS is configured).
There is already code in
Le 23/02/2015 14:27, Julien Puydt a écrit :
Hi,
Le 23/02/2015 12:13, Volker Braun a écrit :
In spkg-install you need to add a suitable branch in configure_base():
Yes, but my question was : how do I know how to write that branch? I
didn't manage to get from configuration import conf to
Le 23/02/2015 15:40, Jean-Pierre Flori a écrit :
I agree with Volker, just put one thing here.
I would say: arch='ARMv6' for base (and arch=ARMv7 for fast if you want
to enable a fast configuration).
It would also be good to put ISA= (don't remember the var name or syntax)
to explicitely
Le 23/02/2015 15:48, Julien Puydt a écrit :
Le 23/02/2015 15:40, Jean-Pierre Flori a écrit :
I agree with Volker, just put one thing here.
I would say: arch='ARMv6' for base (and arch=ARMv7 for fast if you want
to enable a fast configuration).
It would also be good to put ISA= (don't
Yes, exactly!
On Monday, February 23, 2015 at 4:16:40 PM UTC+1, Snark wrote:
If I put something similar in configure_fast, will I be able to test it
looks good using :
export SAGE_ATLAS_ARCH=fast
./sage -f atlas
--
You received this message because you are subscribed to the Google
Le 23/02/2015 16:25, Volker Braun a écrit :
Yes, exactly!
On Monday, February 23, 2015 at 4:16:40 PM UTC+1, Snark wrote:
If I put something similar in configure_fast, will I be able to test it
looks good using :
export SAGE_ATLAS_ARCH=fast
./sage -f atlas
It's ticket #17843. And this
On Saturday, February 21, 2015 at 5:25:07 PM UTC+1, Volker Braun wrote:
The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing else
to see here.
Pointing to a specific location for the atlas library isn't going to be
much use in a binary that we distribute.
On
Le 21/02/2015 14:56, Volker Braun a écrit :
We have an ARM buildbot but it doesn't work: atlas install fails when
SAGE_FAT_BINARY=yes is set. If you have an idea about suitable defaults
then we could make it automatic *hint*
Is there a trac ticket or some such on the matter, with some kind of
The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing else
to see here.
Pointing to a specific location for the atlas library isn't going to be
much use in a binary that we distribute.
On Saturday, February 21, 2015 at 4:54:12 PM UTC+1, Snark wrote:
Le 21/02/2015 14:56,
We have an ARM buildbot but it doesn't work: atlas install fails when
SAGE_FAT_BINARY=yes is set. If you have an idea about suitable defaults
then we could make it automatic *hint*
On Saturday, February 21, 2015 at 2:30:10 PM UTC+1, Snark wrote:
Hi,
is there an ARM build box which will
18 matches
Mail list logo
