[sage-devel] Re: fail to build openblas

2017-02-24 Thread Steven Trogdon
These are the supported X86/X86_64 a)Intel CPU: P2 KATMAI COPPERMINE NORTHWOOD PRESCOTT BANIAS YONAH CORE2 PENRYN DUNNINGTON NEHALEM SANDYBRIDGE HASWELL ATOM I guess you could try 'make TARGET=ATOM'. As a last resort './configure --with-blas=atlas && make'. But I wouldn't do this until all the

[sage-devel] Re: PPL wrapper bug

2017-02-24 Thread jsommars
Thank you, yes, that is exactly what I thought == should give. My mistake, there is no problem. On Friday, February 24, 2017 at 4:23:19 PM UTC-6, Volker Braun wrote: > > sage: Cone1.__cmp__? > Signature: Cone1.__cmp__(right) > Docstring: >Compare "self" and "right". > >INPUT: >

[sage-devel] Re: PPL wrapper bug

2017-02-24 Thread Volker Braun
sage: Cone1.__cmp__? Signature: Cone1.__cmp__(right) Docstring: Compare "self" and "right". INPUT: * "right" -- anything. OUTPUT: * 0 if "self" and "right" are cones of any kind in the same lattice with the same rays listed in the same order. 1 or -1

[sage-devel] Re: PPL wrapper bug

2017-02-24 Thread Dima Pasechnik
On Friday, February 24, 2017 at 7:48:45 PM UTC, jsommars wrote: > > There seems to be a bug in the Parma Polyhedra Library wrapper. > Unfortunately, this is the simplest example I can come up with. > > A=Cone([[0,0,0,1,0],[0,0,1,0,0],[0,1,0,0,0],[1,1,1,1,1],[-1,-1,-1,-1,-1]]) > >

Re: [sage-devel] Re: Trouble with perl_term_readline_gnu

2017-02-24 Thread Simon King
That was quick! Am Freitag, 24. Februar 2017 21:03:12 UTC+1 schrieb Simon King: > > > I'll try again now. > > The previous attempt took about an hour before it failed. Now, it went a lot faster, didn't report an error, and I could do the first few examples from the polymake tutorial! Thank you

Re: [sage-devel] Re: Trouble with perl_term_readline_gnu

2017-02-24 Thread Simon King
Am Freitag, 24. Februar 2017 20:46:59 UTC+1 schrieb vdelecroix: > > On 24/02/2017 20:44, Simon King wrote: > > WARNING: Please install/check the following perl modules prior to > starting polymake: > >XML::Writer, XML::LibXSLT > > You are missing some perl library... from the

Re: [sage-devel] Re: fail to install perl_term_readline_gnu

2017-02-24 Thread Vincent Delecroix
Hi Simon, On 24/02/2017 20:22, Simon King wrote: Hi Vincent, On 2017-02-24, Vincent Delecroix <20100.delecr...@gmail.com> wrote: Dear all, I am reporting an error while installing the package perl_term_readline_gnu on Sage 7.6.beta4. The package is a dependency of polymake. The log is

[sage-devel] PPL wrapper bug

2017-02-24 Thread jsommars
There seems to be a bug in the Parma Polyhedra Library wrapper. Unfortunately, this is the simplest example I can come up with. A=Cone([[0,0,0,1,0],[0,0,1,0,0],[0,1,0,0,0],[1,1,1,1,1],[-1,-1,-1,-1,-1]]) B=Cone([[-1,0,-1,0,0],[-1,0,0,-1,0],[1,0,1,1,0],[1,1,1,1,1],[-1,-1,-1,-1,-1]]) Cone1 =

Re: [sage-devel] Re: Trouble with perl_term_readline_gnu

2017-02-24 Thread Vincent Delecroix
On 24/02/2017 20:44, Simon King wrote: WARNING: Please install/check the following perl modules prior to starting polymake: XML::Writer, XML::LibXSLT You are missing some perl library... from the SPKG.txt you can read """ On Ubuntu, use: sudo apt-get install libxml-libxslt-perl

[sage-devel] Re: fail to install perl_term_readline_gnu

2017-02-24 Thread Simon King
Hi Vincent, On 2017-02-24, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Dear all, > > I am reporting an error while installing the package > perl_term_readline_gnu on Sage 7.6.beta4. The package is a dependency > of polymake. The log is attached and the following error message

Re: [sage-devel] Re: Trouble with perl_term_readline_gnu

2017-02-24 Thread Vincent Delecroix
Could you post the log? ($SAGE_ROOT/logs/pkgs/polymake-VERSION.log) Vincent On 24/02/2017 18:55, Simon King wrote: On 2017-02-24, Simon King wrote: Hi! On 2017-02-24, Simon King wrote: However, I got an error, apparently when trying to

[sage-devel] fail to install perl_term_readline_gnu

2017-02-24 Thread Vincent Delecroix
Dear all, I am reporting an error while installing the package perl_term_readline_gnu on Sage 7.6.beta4. The package is a dependency of polymake. The log is attached and the following error message appears inside I

[sage-devel] Re: Trouble with perl_term_readline_gnu

2017-02-24 Thread Simon King
On 2017-02-24, Simon King wrote: > Hi! > > On 2017-02-24, Simon King wrote: >> However, I got an error, apparently when trying to install a dependency: >> [perl_term_readline_gnu-1.34] Could not find neither libtermcap.a, >> libncurses.a, or

[sage-devel] Re: Trouble with perl_term_readline_gnu

2017-02-24 Thread Simon King
Hi! On 2017-02-24, Simon King wrote: > However, I got an error, apparently when trying to install a dependency: > [perl_term_readline_gnu-1.34] Could not find neither libtermcap.a, > libncurses.a, or libcurses. > [perl_term_readline_gnu-1.34] make[2]: Entering directory

[sage-devel] Trouble with perl_term_readline_gnu

2017-02-24 Thread Simon King
Hi! In preparation of next week's Sage Days, I try to install the experimental polymake package. However, I got an error, apparently when trying to install a dependency: [perl_term_readline_gnu-1.34] Could not find neither libtermcap.a, libncurses.a, or libcurses. [perl_term_readline_gnu-1.34]

[sage-devel] Re: SageNB -> Jupyter conversion needs testers

2017-02-24 Thread Volker Braun
Yay! -- 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.

[sage-devel] SageNB -> Jupyter conversion needs testers

2017-02-24 Thread Jeroen Demeyer
Hello, At https://trac.sagemath.org/ticket/22433 there is a ticket implementing a move from SageNB towards Jupyter. It does conversion of SageNB notebooks to Jupyter, hopefully with little loss of functionality (but I know it's not 100% perfect and it never will be). If you are currently

[sage-devel] Re: [sagemath-admins] Fwd: documentation: activate button?

2017-02-24 Thread Harald Schilly
On Fri, Feb 24, 2017 at 2:44 PM, Luca De Feo wrote: > The "activate" button DOES appear in local installations, if they are > served by the local HTTP server (through the jupyter notebook). Try > it, it's cool. ... well, ok. but what about using the sage cell server

[sage-devel] Fwd: [sagemath-admins] Fwd: documentation: activate button?

2017-02-24 Thread Luca De Feo
The "activate" button DOES appear in local installations, if they are served by the local HTTP server (through the jupyter notebook). Try it, it's cool. It does not appear if you browse the files through the file:/// scheme in your browser. Because of this line:

Re: [sage-devel] Re: documentation: activate button?

2017-02-24 Thread Harald Schilly
On Friday, February 24, 2017 at 2:17:20 PM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > In principle, the activate button > (which transforms examples into cells) should appear when the doc is > browsed from jupyter, not from the online doc. I see, thank you for the pointer, I got it. The

Re: [sage-devel] Re: documentation: activate button?

2017-02-24 Thread Thierry
Hi, On Fri, Feb 24, 2017 at 04:17:33AM -0800, Dima Pasechnik wrote: > > On Friday, February 24, 2017 at 10:54:40 AM UTC, Harald Schilly wrote: > > > > Hello, I just got an issue for the doc.sagemath.org page that there is an > > "Activate" button at the top right and well, I assume it should

[sage-devel] Re: documentation: activate button?

2017-02-24 Thread Dima Pasechnik
On Friday, February 24, 2017 at 10:54:40 AM UTC, Harald Schilly wrote: > > Hello, I just got an issue for the doc.sagemath.org page that there is an > "Activate" button at the top right and well, I assume it should make the > cells alive -- which is really cool -- but it's broken. I haven't

[sage-devel] documentation: activate button?

2017-02-24 Thread Harald Schilly
Hello, I just got an issue for the doc.sagemath.org page that there is an "Activate" button at the top right and well, I assume it should make the cells alive -- which is really cool -- but it's broken. I haven't seen this before and I have no idea what this is about, though. Issue: