Re: [sage-devel] Re: trouble compiling latest sage development version

2016-09-30 Thread Anne Schilling
I am not sure. I just compiled sage-7.3 released 2016-8-04 and it went fine, so I think it must be related to some new patches in the new development branch ... Anne On Friday, September 30, 2016 at 7:08:35 PM UTC-7, François wrote: > > Does the ntl failure look like anything reported at >

Re: [sage-devel] Re: trouble compiling latest sage development version

2016-09-30 Thread Francois Bissey
Does the ntl failure look like anything reported at https://trac.sagemath.org/ticket/20779 ? François > On 1/10/2016, at 14:52, Travis Scrimshaw wrote: > > Perhaps this is from the same error as stack overflow post? I remember we had > to have something with

[sage-devel] Re: trouble compiling latest sage development version

2016-09-30 Thread Travis Scrimshaw
Perhaps this is from the same error as stack overflow post ? I remember we had to have something with '-march=native' (on OSX?) in the past. Best, Travis -- You received this message

[sage-devel] Re: trouble compiling latest sage development version

2016-09-30 Thread Anne Schilling
Hi John, Thanks for your answer, but my git seems to work fine. Even after 'make distclean && make' I still get an error. Here is the log. Any idea? Might this be related to https://trac.sagemath.org/ticket/17635 Best, Anne - Found local metadata for givaro-4.0.2 Using cached file

Re: [sage-devel] Re: openblas segfault?

2016-09-30 Thread Jonathan Bober
I got around to trying the latest OpenBLAS as Jean-Pierre Flori suggested, and the segfaults went away. (And all tests pass.) I guess that from my perspective this means I should open an "update to OpenBLAS 0.2.19" ticket. Or maybe it should be an "Update OpenBLAS to some working version" ticket.

[sage-devel] Re: trouble compiling latest sage development version

2016-09-30 Thread John H Palmieri
Hi Anne, Here's a complete shot in the dark: has Xcode been updated recently on that machine, maybe automatically when you didn't notice? If you run "git status" (using the system's git) and it gives some funny error message about root access, this is what's going on. Run Xcode, agree to the

[sage-devel] trouble compiling latest sage development version

2016-09-30 Thread Anne Schilling
Hi! I am having trouble compiling the latest sage development branch: ... [openblas-0.2.15] correctly and load a subshell for you to debug the error: [openblas-0.2.15] (cd '/Applications/sage/local/var/tmp/sage/build/openblas-0.2.15' && '/Applications/sage/sage' --sh) [openblas-0.2.15] When

Re: [sage-devel] Problem in setup sage server

2016-09-30 Thread William Stein
On Fri, Sep 30, 2016 at 9:58 AM, B Krishnan Iyer wrote: > I followed the steps shown in the link:https://wiki.sagemath.org/SageServer > > while entering 'sudo apt-get install python-software-properties' it is > asking for password so can someone tell me what the password

[sage-devel] Problem in setup sage server

2016-09-30 Thread B Krishnan Iyer
I followed the steps shown in the link: *https://wiki.sagemath.org/SageServer *while entering 'sudo apt-get install python-software-properties' it is asking for password so can someone tell me what the password is?. Also this command 'sudo -u sageserver

[sage-devel] Re: How find out which plot causes docbuild error

2016-09-30 Thread Ralf Stephan
On Friday, September 30, 2016 at 4:50:01 PM UTC+2, John H Palmieri wrote: > > In a perfect world, 1937 would be a line number, either in the original > python file or in the rst file. Try looking there. > The actual rst file is not the one that is autogenerated from the docs, probably in memory.

[sage-devel] Re: How find out which plot causes docbuild error

2016-09-30 Thread John H Palmieri
In a perfect world, 1937 would be a line number, either in the original python file or in the rst file. Try looking there. John On Friday, September 30, 2016 at 12:20:43 AM UTC-7, Ralf Stephan wrote: > > Hi, > > [dochtml] OSError: [plot3d ] >

Re: [sage-devel] How find out which plot causes docbuild error

2016-09-30 Thread Ralf Stephan
Thanks! -- 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.

Re: [sage-devel] How find out which plot causes docbuild error

2016-09-30 Thread Francois Bissey
A fair question. I cannot remember the folder from the top of my head but I have debugged that problem several time. First counting 35 blocks may not get you the right one, unless you are building serially. You should try to locate it under

[sage-devel] How find out which plot causes docbuild error

2016-09-30 Thread Ralf Stephan
Hi, [dochtml] OSError: [plot3d ] /home/ralf/sage/src/doc/en/reference/plot3d/sage/plot/plot3d/plot3d.rst:1937: WARNING: Exception occurred in plotting plot3d-35 how do I find out without manipulating the rst or counting 35 blocks which plot has failed? This is a principle question, I could