Re: [sage-devel] Re: [ARM] sage 6.5
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 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.
Re: [sage-devel] Re: Sage 6.5, pyzmq, Fedora GCC
On Monday, February 23, 2015 at 10:36:40 AM UTC+1, Jori Mantysalo wrote: Did you test on Fedora 21 server on Fedora 21 normal version? At server version, and after installing m4, binutils, perl, gcc and gfortran I got error about cpp sanity check failing. post the log -- 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.
Re: [sage-devel] [debian] Strange numerical errors in sage's libpari code
On 2015-02-23 11:05, John Cremona wrote: It is rather hard to write all such doctests to be invariant under such things, especially as doctests also serve as examples for the reference manual, so you really do want such an example which computes fundamental units *and displays them* as a user would expect. We could change the default representation of ideals such that a uniquely defined generator is shown instead of whatever PARI answers. For example: if PARI gives g as generator of the ideal, then try g*u for all roots of unity(*) u and take the one with the shortest string representation for example. (*) In practice, variation is by roots of unity, most often even just the sign. We could also do something with fundamental units, but then it becomes more difficult to uniquely define a generator. -- 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 is currently toying with the following patch :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..b5c2808 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,12 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+if conf['processor'] == 'armv7l':
+arch = 'ARMv7'
+else:
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
Does it look good?
What about that one :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..7733f65 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,13 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+if conf['processor'] == 'armv7l':
+print('Base configuration on ARMv7.')
+arch = 'ARMv7'
+else:
+print('Base configuration on ARMv6.')
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
?
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.
Re: [sage-devel] Re: Sage 6.5, pyzmq, Fedora GCC
On Mon, 23 Feb 2015, Volker Braun wrote: post the log Duh. There was no c++ compiler installed. It seems that configure continues after not founding g++; contrary to this, if ar is not found, configure stops (and last error message is meaningful). I am now compiling without parallel compiling and on fresh installation of Fedora 21 server. If I don't write write more to this thread, everything went OK. * * * As a side note: to get Sage compiling, I must say yum install binutils gcc gcc-c++ gcc-gfortran m4 perl I think that there was some discussion about m4 several months ago. -- Jori Mäntysalo This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by Sage configure 6.5.rc2, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --disable-compiler-checks ## - ## ## Platform. ## ## - ## hostname = localhost.localdomain uname -m = x86_64 uname -r = 3.17.4-301.fc21.x86_64 uname -s = Linux uname -v = #1 SMP Thu Nov 27 19:09:10 UTC 2014 /usr/bin/uname -p = x86_64 /bin/uname -X = unknown /bin/arch = x86_64 /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /home/user/sage-6.5/src/bin PATH: /home/user/sage-6.5/local/bin PATH: /usr/local/bin PATH: /bin PATH: /usr/bin PATH: /usr/local/sbin PATH: /usr/sbin PATH: /home/user/.local/bin PATH: /home/user/bin ## --- ## ## Core tests. ## ## --- ## configure:2354: checking for a BSD-compatible install configure:2422: result: /bin/install -c configure:2433: checking whether build environment is sane configure:2488: result: yes configure:2639: checking for a thread-safe mkdir -p configure:2678: result: /bin/mkdir -p configure:2685: checking for gawk configure:2701: found /bin/gawk configure:2712: result: gawk configure:2723: checking whether make sets $(MAKE) configure:2745: result: yes configure:2774: checking whether make supports nested variables configure:2791: result: yes configure:2919: checking whether to enable maintainer-specific portions of Makefiles configure:2928: result: yes configure:2945: checking for root user configure:2954: result: no configure:2994: checking build system type configure:3008: result: x86_64-unknown-linux-gnu configure:3028: checking host system type configure:3041: result: x86_64-unknown-linux-gnu configure:3172: checking for ar configure:3188: found /bin/ar configure:3200: result: yes configure:3221: checking for m4 configure:3237: found /bin/m4 configure:3249: result: yes configure:3270: checking for ranlib configure:3286: found /bin/ranlib configure:3298: result: yes configure:3319: checking for strip configure:3335: found /bin/strip configure:3347: result: yes configure:3367: checking for GNU or BSD tar configure:3415: result: /bin/tar configure:3482: checking for latex configure:3510: result: no configure:3520: WARNING: You do not have 'latex', which is recommended, but not configure:3522: WARNING: required. Latex is only really used for building pdf configure:3524: WARNING: documents and for %latex mode in the Sage notebook. configure:3534: checking for perl configure:3552: found /bin/perl configure:3564: result: /bin/perl configure:3572: checking for Perl version 5.8.0 or later configure:3583: result: yes configure:3599: checking for dpkg configure:3627: result: no configure:3637: checking for dpkg-architecture configure:3665: result: no configure:3744: checking for gcc configure:3771: result: gcc configure:4000: checking for C compiler version configure:4009: gcc --version 5 gcc (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:4020: $? = 0 configure:4009: gcc -v 5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.9.2/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.9.2-20150212/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.9.2-20150212/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Re: [sage-devel] Re: [ARM] sage 6.5
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 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 is currently toying with the following patch :
diff --git a/build/pkgs/atlas/spkg-install
b/build/pkgs/atlas/spkg-install
index 2d2972e..b5c2808 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,12 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+if conf['processor'] == 'armv7l':
+arch = 'ARMv7'
+else:
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
Does it look good?
What about that one :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..7733f65 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,13 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+if conf['processor'] == 'armv7l':
+print('Base configuration on ARMv7.')
+arch = 'ARMv7'
+else:
+print('Base configuration on ARMv6.')
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
?
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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 values I have in there on my ARM box. Now I have found the time do dig around, and found configuration.py just right there in build/pkgs/atlas/, so I think I'll be able to do something :-P That will take some time though : this box isn't fast. And I work on it while it plays with sage. 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.
Re: [sage-devel] Re: Sage-6.5 Source Fails to Compile
Nobody should use -Werror on production compiles. I consider this an upstream bug. -- 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.
[sage-devel] Re: [ARM] sage 6.5
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 compile ad nauseum so it doesn't
take that much time.
The box is currently toying with the following patch :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..b5c2808 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,12 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+if conf['processor'] == 'armv7l':
+arch = 'ARMv7'
+else:
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
Does it look good?
What about that one :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..7733f65 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,13 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+if conf['processor'] == 'armv7l':
+print('Base configuration on ARMv7.')
+arch = 'ARMv7'
+else:
+print('Base configuration on ARMv6.')
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
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).
Dima
--
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.
[sage-devel] Re: [ARM] sage 6.5
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. 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 is currently toying with the following patch :
diff --git a/build/pkgs/atlas/spkg-install
b/build/pkgs/atlas/spkg-install
index 2d2972e..b5c2808 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,12 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+if conf['processor'] == 'armv7l':
+arch = 'ARMv7'
+else:
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
Does it look good?
What about that one :
diff --git a/build/pkgs/atlas/spkg-install
b/build/pkgs/atlas/spkg-install
index 2d2972e..7733f65 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,13 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+if conf['processor'] == 'armv7l':
+print('Base configuration on ARMv7.')
+arch = 'ARMv7'
+else:
+print('Base configuration on ARMv6.')
+arch = 'ARMv6'
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 disable isa extensions for the base configuration.
I would have to think more to remember what to put for the fast
configuration.
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
hmm, shouldn't there also be a distinction between hardware and software
floats?
I'd say no.
If you really want soft floats, then you're on your own.
Same same if you want to build on something armv6.
--
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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 spkg-install to force hf on ARM -- I didn't touch that. 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 work, so I
couldn't look at 'conf' to know what values I have in there on my ARM box.
Now I have found the time do dig around, and found configuration.py just
right there in build/pkgs/atlas/, so I think I'll be able to do
something :-P
That will take some time though : this box isn't fast. And I work on it
while it plays with sage.
The box is currently toying with the following patch :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..b5c2808 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,12 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+if conf['processor'] == 'armv7l':
+arch = 'ARMv7'
+else:
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
Does it look good?
We should have the time to discuss before the compilation finishes...
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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 disable isa extensions for the base configuration.
I would have to think more to remember what to put for the fast
configuration.
For the base, isa_ext is set to none at the start of the config_base
function.
I'm now trying on my armv7l box with the ARMv6 arch :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..f201c42 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,9 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
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.
[sage-devel] Re: Sage Enhancement Proposal: Edwards Curves Library
I'm a bit ignorant about Edwards models. I understood its main usefulness was because it was faster than the usual models, requiring less arithmetic operations. Given that this was the primary usefulness, wouldn't it make sense to compare your library with some other fast libraries to show that it is actually faster. For example, why not use Dan Bernstein's highly optimised code. On the other hand, if there are theoretically interesting problems that can be studied only with the Edwards model, then there would be a reason to include it no matter what the practical performance is. Bill. On Saturday, 21 February 2015 06:13:31 UTC+1, Adarsh Saraf wrote: Hi Martin, Basically the module that I have written implements the Edwards model as an 'EdwardsCurve' class with an accompanying EdwardsCurvePoint class. For the methods that I have implemented, I have tried to mimic those in the Elliptic Curves library already in Sage. But I do not have different classes for the different types of base fields for it was not necessary for my work. Once I have added a patch and people feel that it would be better to have these classes, then we can easily do that too. Plus, I am also thinking of adding the documentation mimicking that for Elliptic Curves. The main functions that I have implemented as of now are: 1. Point addition 2. Scalar multiplication 3. Additive order of the points 4. Returning random points on the curve 5. Returning the n-torsion subgroup given n 6. Returning all the points on the curve in the finite field setting 7. Returning the isomorphic Weierstrass model as an 'EllipticCurve' object These are my further plans: 1. Have a method to obtain an 'EdwardsCurve' given a Weierstrass curve, after the base field extension if necessary 2. Implement the analogues of Velu's formulae for computing an isogeny given the kernel generators Adarsh. -- 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 remember the var name or
syntax)
to explicitely disable isa extensions for the base configuration.
I would have to think more to remember what to put for the fast
configuration.
For the base, isa_ext is set to none at the start of the config_base
function.
I'm now trying on my armv7l box with the ARMv6 arch :
diff --git a/build/pkgs/atlas/spkg-install b/build/pkgs/atlas/spkg-install
index 2d2972e..f201c42 100755
--- a/build/pkgs/atlas/spkg-install
+++ b/build/pkgs/atlas/spkg-install
@@ -392,6 +392,9 @@ def configure_base():
elif conf['IA64?']:
print('Base configuration on Itanium.')
arch = 'IA64Itan'
+elif conf['ARM?']:
+print('Base configuration on ARM.')
+arch = 'ARMv6'
else:
raise NotImplementedError('I don\'t know a base
configuration for your cpu.')
return (arch, isa_ext, thread_limit)
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
?
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.
Re: [sage-devel] Re: Sage Enhancement Proposal: Edwards Curves Library
2015-02-23 15:54 UTC+01:00, Bill Hart goodwillh...@googlemail.com: On the other hand, if there are theoretically interesting problems [...] Pedagogical purpose can be fine as well. But in that case, the documentation has to be irreproachable. Vincent -- 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 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.
[sage-devel] Re: GSoC projects
Am 13.02.2015 um 17:04 schrieb mmarco: Apperently there have been some movement on that aspect on sympy too: Yes, but unfortunately no GSoC students worked on this. They also have no CAD yet, see https://github.com/sympy/sympy/wiki/GSoC-2015-Ideas#cylindrical-algebraic-decomposition . -- 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.
[sage-devel] documentation coverage report
Hello, Because of #17841 we can get global statistics of documentation coverage... and right now Global score: 94.4% (35344 of 37421) 401 files with wrong documentation 1514 functions with no doc 563 functions with no test 310 doctest are potentially wrong Vincent -- 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 time it looks like I managed to attach a branch without naming it help (or anything inappropriate). 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.
Re: [sage-devel] Re: Sage Enhancement Proposal: Edwards Curves Library
I think this would be for pedagogical purposes. There would be no point (that I can see) in duplicating all the functionality now available for Weierstrass models. Obvioulsy Bernstein's optimised formulas should be used, otherwise there is really little point. But don't artificially restrict to finite fields. John On 23 February 2015 at 15:04, Vincent Delecroix 20100.delecr...@gmail.com wrote: 2015-02-23 15:54 UTC+01:00, Bill Hart goodwillh...@googlemail.com: On the other hand, if there are theoretically interesting problems [...] Pedagogical purpose can be fine as well. But in that case, the documentation has to be irreproachable. Vincent -- 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. -- 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.
[sage-devel] Re: GSoC projects
I think it would make more sense to wrap qepcad than to rewrite its functionality from scratch. Of course, SymPy doesn't follow the same approach as Sage, so i guess for them it makes sense to reinvent the wheel. El lunes, 23 de febrero de 2015, 17:13:38 (UTC+1), robert.pollak escribió: Am 13.02.2015 um 17:04 schrieb mmarco: Apperently there have been some movement on that aspect on sympy too: Yes, but unfortunately no GSoC students worked on this. They also have no CAD yet, see https://github.com/sympy/sympy/wiki/GSoC-2015-Ideas#cylindrical-algebraic-decomposition . -- 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.
[sage-devel] Re: documentation coverage report
401 files with wrong documentation I couldn't get a good sense of what wrong meant from that patch. What does that specifically refer to? Thanks, - kcrisman -- 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.
[sage-devel] Re: documentation coverage report
On Monday, February 23, 2015 at 10:07:13 AM UTC-8, kcrisman wrote: I couldn't get a good sense of what wrong meant from that patch. What does that specifically refer to? I wondered about that too. Apparently, it's sage --coverage jargon. A doctest is possibly wrong if the name of the doctested function doesn't occur in the doctest. I was having a faint hope of being impressed with our automatic documentation testing. If we could automatically distinguish correct documentation from wrong documentation, we could just solve our documentation woes by letting the tester run over all possible docstrings and pick out the correct documentation. Naturally, the concept turned out a little more mundane than that. -- 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.
[sage-devel] Sage Days during Mar 21-29, 2015?
Hi, How many people would be interested in a Sage days in (very nice sunny) Seattle during Mar 21-29, 2015, a month from now? This is during UW's spring break, so we would have plenty of space on campus. This would be all expenses paid for all US people (unfortunately the grant only covers them). This could be on a mix of themes of interest (from number theory to bug fixing to education to the cloud to whatever) -- it doesn't have to be on any specific topic. -- William -- William (http://wstein.org) -- 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.
[sage-devel] Re: Sage Days during Mar 21-29, 2015?
I have teaching duties that week, so, unfortunately, i can't go. El lunes, 23 de febrero de 2015, 19:06:31 (UTC+1), William escribió: Hi, How many people would be interested in a Sage days in (very nice sunny) Seattle during Mar 21-29, 2015, a month from now? This is during UW's spring break, so we would have plenty of space on campus. This would be all expenses paid for all US people (unfortunately the grant only covers them). This could be on a mix of themes of interest (from number theory to bug fixing to education to the cloud to whatever) -- it doesn't have to be on any specific topic. -- William -- William (http://wstein.org) -- 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.
[sage-devel] Re: missing changelog
There is currently a 404 for http://sagemath.org/mirror/src/changelogs/sage-6.5.txt which is linked from http://sagemath.org/ Yes, there is always a slight delay in creating this because the creation is no longer an automated part of the process. The finalized version should be up soon, Harald has a link for 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...@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.
[sage-devel] Re: how to unsubscribe from Trac ticket updates
On 2015-02-21, Volker Braun vbraun.n...@gmail.com wrote: http://trac.edgewall.org/ticket/9971 Thanks, it's comforting to hear it's a known problem. See also the discussion at: https://code.djangoproject.com/ticket/16763 Apparently a key configuration variable, given the current notification system, is always_notify_updater; when it's turned off, notifications are sent only to the cc list, I gather. best Robert Dodier -- 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.
Re: [sage-devel] Re: Addition of zero in the coercion model
Hi In my case there is a cm.coercion_map(parent(myElement), parent(0)) (line 907) namely the coercions into the modular forms ring. These maps are then used to map both myElement and 0 to the modular forms ring (in contrast to the (vector) space myElement.parent()). Unfortunately the check for the special case 0 comes after this, not before. :-( Regards Jonas On 22.02.2015 16:39, Simon King wrote: Hi Eric, On 2015-02-22, Eric Gourgoulhon egourgoul...@gmail.com wrote: Note that the function is_Integer used in sage.structure.coerce.pyx is=20 *not* the above one: it is defined in lines 134-139 and it returns True for= is_Integer(int(0)).=20 Seriously? But when the integer zero is treated in a special way, then why did sum(...) not work in the original post, while sum(..., P.zero()) did? Best regards, Simon -- 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.
[sage-devel] Re: documentation coverage report
Hi Karl-Dieter, On 2015-02-23, kcrisman kcris...@gmail.com wrote: There is even a tag (I forget the exact wording) for saying that this is an indirect doctest, which hopefully this script picks out. sage: I think the tag it is # indirect doctest Cheers, Simon -- 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.
[sage-devel] Re: documentation coverage report
There is even a tag (I forget the exact wording) for saying that this is an indirect doctest, which hopefully this script picks out. On Monday, February 23, 2015 at 1:22:51 PM UTC-5, Nils Bruin wrote: On Monday, February 23, 2015 at 10:07:13 AM UTC-8, kcrisman wrote: I couldn't get a good sense of what wrong meant from that patch. What does that specifically refer to? I wondered about that too. Apparently, it's sage --coverage jargon. A doctest is possibly wrong if the name of the doctested function doesn't occur in the doctest. I was having a faint hope of being impressed with our automatic documentation testing. If we could automatically distinguish correct documentation from wrong documentation, we could just solve our documentation woes by letting the tester run over all possible docstrings and pick out the correct documentation. Naturally, the concept turned out a little more mundane than that. -- 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.
[sage-devel] Re: coercion of objects embedded in symbolic expressions
On Sunday, February 22, 2015 at 1:03:54 PM UTC+1, Burcin Erocal wrote: Pynac already calls the Python comparison function if both are pyobjects. In this case, infinity and constants are not pyobjects. They are a basic class as in mul, add, symbol, etc. The code need not be fast so my solution is in Python and utilizes the InfinityRing. http://trac.sagemath.org/ticket/12967 -- 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.
[sage-devel] Re: matrix_template.pyx
On 2015-02-23, Clemens Heuberger clemens.heuber...@aau.at wrote: http://www.sagemath.org/doc/reference/matrices/sage/matrix/docs.html#implementation-and-design mentions See the files matrix_template.pxd and matrix_template.pyx. However, I could not find these files. Could you open a trac ticket on this? Thanks! If they do not exist: is there a recommended example to follow when I implement bindings for arb's acb_mat class? (#17220). Thank you, CH -- 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.
Re: [sage-devel] Re: Sage 6.5, pyzmq, Fedora GCC
On Fri, 20 Feb 2015, Volker Braun wrote: You need to build the zeromq library before building the python binding for it: sage -f zeromq sage -f pyzmq Definitely works on Fedora 21 I don't quite understand. I was building whole Sage, not just one package. Did you test on Fedora 21 server on Fedora 21 normal version? At server version, and after installing m4, binutils, perl, gcc and gfortran I got error about cpp sanity check failing. But maybe I should first test with workstation version. -- Jori Mäntysalo
[sage-devel] matrix_template.pyx
http://www.sagemath.org/doc/reference/matrices/sage/matrix/docs.html#implementation-and-design mentions See the files matrix_template.pxd and matrix_template.pyx. However, I could not find these files. If they do not exist: is there a recommended example to follow when I implement bindings for arb's acb_mat class? (#17220). Thank you, CH -- 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.
Re: [sage-devel] [debian] Strange numerical errors in sage's libpari code
Hi, Le 18/02/2015 13:53, Julien Puydt a écrit : I'm having strange numerical behaviour with my experimental sage using debian packages, with two failing doctests in the src/sage/libs/pari/ directory (both in gen.pyx) : Failed example: (s*z)^5 Expected: 2.00 - 1.08420217248550 E-19*I Got: 2.00 + 0.E-19*I Failed example: e.ellztopoint(1+i) Expected: [0.E-19 - 1.02152286795670*I, -0.149072813701096 - 0.149072813701096*I] Got: [0.E-18 - 1.02152286795670*I, -0.149072813701096 - 0.149072813701096*I] If those are indeed more numerical noise than serious issues, how can one relax the doctests so they don't fail at each pari upgrade, but still detect big problems ? I don't think a simple # tol 1e-15 will do the trick here, will it ? 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.
Re: [sage-devel] Re: Addition of zero in the coercion model
Hi, Le dimanche 22 février 2015 21:25:02 UTC+1, Jeroen Demeyer a écrit : On the other, this special case is consistent with the idea of the univeral 0 object proposed by John Cremona. Indeed. In this respect, it is probably safe to use the literal 0 provided one makes sure that it is treated as Integer(0) (Sage interpreter) *or* int(0) (Python code), which sage.structure.coerce.pyx does properly (via its function is_Integer). Best wishes, Eric. -- 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.
Re: [sage-devel] matrix_template.pyx
I would look at matrix_integer_dense.pyx which wraps fmpz_mat from flint (which looks even better after #17822 (needs review)). Are there also arb's polynomial? Vincent 2015-02-23 9:56 UTC+01:00, Clemens Heuberger clemens.heuber...@aau.at: http://www.sagemath.org/doc/reference/matrices/sage/matrix/docs.html#implementation-and-design mentions See the files matrix_template.pxd and matrix_template.pyx. However, I could not find these files. If they do not exist: is there a recommended example to follow when I implement bindings for arb's acb_mat class? (#17220). Thank you, CH -- 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. -- 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.
Re: [sage-devel] matrix_template.pyx
On 2015-02-23 10:59, Vincent Delecroix wrote: I would look at matrix_integer_dense.pyx which wraps fmpz_mat from flint (which looks even better after #17822 (needs review)). thanks for the hint. Are there also arb's polynomial? Yes, arb provides polynomials http://fredrikj.net/arb/arb_poly.html , http://fredrikj.net/arb/acb_poly.html , however, I do not plan to write sage bindings in the foreseeable future. Regards, Clemens -- 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.
[sage-devel] missing changelog
There is currently a 404 for http://sagemath.org/mirror/src/changelogs/sage-6.5.txt which is linked from http://sagemath.org/ Ralf -- 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.
Re: [sage-devel] Re: matrix_template.pyx
On 2015-02-23 11:25, Dima Pasechnik wrote: On 2015-02-23, Clemens Heuberger clemens.heuber...@aau.at wrote: http://www.sagemath.org/doc/reference/matrices/sage/matrix/docs.html#implementation-and-design mentions See the files matrix_template.pxd and matrix_template.pyx. However, I could not find these files. Could you open a trac ticket on this? Thanks! http://trac.sagemath.org/ticket/17836 For simplicity, I attached a branch deleting the reference; however, providing the two files would be welcome (but I cannot do it). Regards, CH -- 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.
Re: [sage-devel] Re: [ARM] sage 6.5
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 Saturday, February 21, 2015 at 4:54:12 PM UTC+1, Snark wrote: 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* ARMv7 for base? maybe ARMv6 so that raspberry pi's get supported. Not sure about fast, maybe ARMv7+NEON? Didn't I put some archdefs into our ATLAS tarball at some point? http://trac.sagemath.org/ticket/15615 Not sure what was exactly inside. -- 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.
Re: [sage-devel] [debian] Strange numerical errors in sage's libpari code
On 23 February 2015 at 09:23, Julien Puydt julien.pu...@laposte.net wrote: Hi, Le 18/02/2015 13:53, Julien Puydt a écrit : I'm having strange numerical behaviour with my experimental sage using debian packages, with two failing doctests in the src/sage/libs/pari/ directory (both in gen.pyx) : Failed example: (s*z)^5 Expected: 2.00 - 1.08420217248550 E-19*I Got: 2.00 + 0.E-19*I Failed example: e.ellztopoint(1+i) Expected: [0.E-19 - 1.02152286795670*I, -0.149072813701096 - 0.149072813701096*I] Got: [0.E-18 - 1.02152286795670*I, -0.149072813701096 - 0.149072813701096*I] If those are indeed more numerical noise than serious issues, how can one relax the doctests so they don't fail at each pari upgrade, but still detect big problems ? These ones are certainly numerical noise. We always get these with pari upgrades. The other thing which happens a lot after pari upgrades is that computations for which there is more than one correct answer (e.g. fundamental units of a number field, which are generators for a group and so never unique except in special cases) give a different correct answer, which at the moment requires a human to verify are still OK. These things propogate of course. It is rather hard to write all such doctests to be invariant under such things, especially as doctests also serve as examples for the reference manual, so you really do want such an example which computes fundamental units *and displays them* as a user would expect. (For that example, we could put a #random tag on the units output, while also adding an assertion that the regulator -- an invariant real number associated to units -- was correct to within some tolerance. Doing this everywhere would take alot of effort, though it may save in the long term. John I don't think a simple # tol 1e-15 will do the trick here, will it ? 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. -- 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.
Re: [sage-devel] matrix_template.pyx
2015-02-23 10:46 UTC+01:00, Clemens Heuberger clemens.heuber...@aau.at: On 2015-02-23 10:59, Vincent Delecroix wrote: I would look at matrix_integer_dense.pyx which wraps fmpz_mat from flint (which looks even better after #17822 (needs review)). thanks for the hint. Are there also arb's polynomial? Yes, arb provides polynomials http://fredrikj.net/arb/arb_poly.html , http://fredrikj.net/arb/acb_poly.html , Cool! however, I do not plan to write sage bindings in the foreseeable future. Too bad! I will have a look once the interface is stabilized. It would be really useful for #17830. Vincent -- 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.
[sage-devel] remove optional packages: extra_docs-20070208, java3d-20070901, knoboo-20080411
Hi, I propose that we remove the optional package extra_docs-20070208 from sage completely. It's static copies of documentation from 8 years ago relevant to sage. It's a package I made. Clearly I'm not updating it. I also think we should remove java3d-20070901 and knoboo-20080411. In fact, I would be OK with removing all of the following as official optional Sage packages that appear when doing sage -optional on a fresh sage-6.5 install: salvus@compute:/usr/local/sage/sage-6.5$ ./sage -optional|grep not PyQt_x11-4.9.1.p0 ... not installed TOPCOM-0.17.4 ... not installed autotools-20121217 .. not installed beautifulsoup-3.2.1 . not installed # in pypi extra_docs-20070208 . not installed gcc-4.6.4 ... not installed # doesn't standard sage have a newer gcc? ginv-1.9-20080723 ... not installed # dated java3d-20070901 . not installed # surely broken/useless knoboo-20080411 . not installed # ancient libogg-1.1.4 not installed libtheora-1.1.1 . not installed mpi4py-1.2.2 not installed openmpi-1.4.3 ... not installed openssl-1.0.1c.p0 ... not installed sip-4.13.2.p0 ... not installed trac-0.11.5.p0 .. not installed -- 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.
Re: [sage-devel] Re: Sage Days during Mar 21-29, 2015?
I have teaching duties that week, so, unfortunately, i can't go. Same here. When is your Spring Break? Just a couple weeks from now, and already spoken for :) sorry :( because I would be interested in a dedicated Sage time right now, which I don't have now. -- 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.
[sage-devel] Re: remove optional packages: extra_docs-20070208, java3d-20070901, knoboo-20080411
In fact, I would be OK with removing all of the following as official optional Sage packages that appear when doing sage -optional on a fresh sage-6.5 install: beautifulsoup-3.2.1 . not installed # in pypi Then we would need to update some documentation and so forth. gcc-4.6.4 ... not installed # doesn't standard sage have a newer gcc? Yes ginv-1.9-20080723 ... not installed # dated java3d-20070901 . not installed # surely broken/useless http://trac.sagemath.org/ticket/16647 knoboo-20080411 . not installed # ancient yes libogg-1.1.4 not installed libtheora-1.1.1 . not installed maybe? Worth keeping on the server, I think. openssl-1.0.1c.p0 ... not installed is that because we have the updated package? trac-0.11.5.p0 .. not installed yes -- 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.
[sage-devel] Re: Sage Days during Mar 21-29, 2015?
I have teaching duties that week, so, unfortunately, i can't go. Same here. -- 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.
Re: [sage-devel] Re: Sage Days during Mar 21-29, 2015?
On Mon, Feb 23, 2015 at 6:00 PM, kcrisman kcris...@gmail.com wrote: I have teaching duties that week, so, unfortunately, i can't go. Same here. When is your Spring Break? -- William -- 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. -- William (http://wstein.org) -- 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.
[sage-devel] Two 14.04 binaries
Hi What is the difference between the lmza and lrz files? ftp://ftp.sun.ac.za/pub/mirrors/www.sagemath.org/linux/64bit/index.html Besides the obvious difference in compression. Regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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.
