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 last):
File "./spkg-install", line 510, in <module>
rc = build()
File "./spkg-install", line 448, in build
rc = configure(arch, isa_ext)
File "./spkg-install", line 256, in configure
arch, isa_ext, thread_limit = configure_base()
File "./spkg-install", line 396, in configure_base
raise NotImplementedError('I don\'t know a "base" configuration for
your cpu.')
NotImplementedError: I don't know a "base" configuration for your cpu.
I think something should be done in the configure_base function -- but
since I haven't found how "from configuration import conf" works, I
don't know exactly how to make that work.
Pointing to a specific location for the atlas library isn't going to be
much use in a binary that we distribute.
As pointed out by J.-P. Flori, "ARM" is a generic name for a whole
processor family, so providing something which works everywhere isn't
easy... or even possible.
Still, we can perhaps shoot for something better.
Snark on #sagemath
--
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, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
