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

[Anne Schilling]

I reinstalled all of XCode now (not just the command line version) and sage 
compiles again! Yippieh! Thank you all for your help!

Anne

On Tuesday, October 11, 2016 at 9:18:22 PM UTC-7, François wrote:
>
> Ok the initial problem was with avx instructions. Either givaro gets 
> misconfigured in thinking you have avx or someone you get a broken 
> assembler. 
> Can you try 
> CXXFLAGS=“-Wa,-q” ./sage -i givaro 
>
> > On 12/10/2016, at 16:41, Anne Schilling  > wrote: 
> > 
> > Wait, isn't this the error I started with before I upgraded to OSX 10.12 
> etc? I seem to be going in circles. 
> > Is this related to https://trac.sagemath.org/ticket/17635? 
> > 
> > Cheers, 
> > 
> > Anne 
> > 
> > On Tuesday, October 11, 2016 at 8:35:39 PM UTC-7, Anne Schilling wrote: 
> > Hi John, 
> > 
> > Thank you for the answer! I did what you suggested and this time, sage 
> started compiling and got to here: 
> > 
> >  
> > [gf2x-1.1.p1] make[5]: Nothing to be done for `install-exec-am'. 
> > [gf2x-1.1.p1] make[5]: Nothing to be done for `install-data-am'. 
> > [gf2x-1.1.p1] Making install in src 
> > [gf2x-1.1.p1] make  install-am 
> > [gf2x-1.1.p1] make[6]: Nothing to be done for `install-exec-am'. 
> > [gf2x-1.1.p1] make[6]: Nothing to be done for `install-data-am'. 
> > [gf2x-1.1.p1] 
> > [gf2x-1.1.p1] real4m35.653s 
> > [gf2x-1.1.p1] user4m21.480s 
> > [gf2x-1.1.p1] sys0m14.484s 
> > [gf2x-1.1.p1] Successfully installed gf2x-1.1.p1 
> > [gf2x-1.1.p1] Deleting temporary build directory 
> > [gf2x-1.1.p1] /Applications/sage/local/var/tmp/sage/build/gf2x-1.1.p1 
> > [gf2x-1.1.p1] Finished installing gf2x-1.1.p1.spkg 
> > make[1]: *** [all] Error 2 
> > 
> > real36m26.897s 
> > user95m0.211s 
> > sys12m51.527s 
> > *** 
> > Error building Sage. 
> > 
> > The following package(s) may have failed to build (not necessarily 
> > during this run of 'make all'): 
> > 
> > * package: givaro-4.0.2 
> >   log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log 
> >   build directory: 
> /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2 
> > 
> > The build directory may contain configuration files and other 
> potentially 
> > helpful information. WARNING: if you now run 'make' again, the build 
> > directory will, by default, be deleted. Set the environment variable 
> > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. 
> > 
> > make: *** [all] Error 1 
> > 
> > Any further ideas? 
> > 
> > Anne 
> >   
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Francois Bissey]

Ok the initial problem was with avx instructions. Either givaro gets
misconfigured in thinking you have avx or someone you get a broken assembler.
Can you try
CXXFLAGS=“-Wa,-q” ./sage -i givaro

> On 12/10/2016, at 16:41, Anne Schilling  wrote:
> 
> Wait, isn't this the error I started with before I upgraded to OSX 10.12 etc? 
> I seem to be going in circles.
> Is this related to https://trac.sagemath.org/ticket/17635?
> 
> Cheers,
> 
> Anne
> 
> On Tuesday, October 11, 2016 at 8:35:39 PM UTC-7, Anne Schilling wrote:
> Hi John,
> 
> Thank you for the answer! I did what you suggested and this time, sage 
> started compiling and got to here:
> 
> 
> [gf2x-1.1.p1] make[5]: Nothing to be done for `install-exec-am'.
> [gf2x-1.1.p1] make[5]: Nothing to be done for `install-data-am'.
> [gf2x-1.1.p1] Making install in src
> [gf2x-1.1.p1] make  install-am
> [gf2x-1.1.p1] make[6]: Nothing to be done for `install-exec-am'.
> [gf2x-1.1.p1] make[6]: Nothing to be done for `install-data-am'.
> [gf2x-1.1.p1] 
> [gf2x-1.1.p1] real4m35.653s
> [gf2x-1.1.p1] user4m21.480s
> [gf2x-1.1.p1] sys0m14.484s
> [gf2x-1.1.p1] Successfully installed gf2x-1.1.p1
> [gf2x-1.1.p1] Deleting temporary build directory
> [gf2x-1.1.p1] /Applications/sage/local/var/tmp/sage/build/gf2x-1.1.p1
> [gf2x-1.1.p1] Finished installing gf2x-1.1.p1.spkg
> make[1]: *** [all] Error 2
> 
> real36m26.897s
> user95m0.211s
> sys12m51.527s
> ***
> Error building Sage.
> 
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
> 
> * package: givaro-4.0.2
>   log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
>   build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2
> 
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
> 
> make: *** [all] Error 1
> 
> Any further ideas?
> 
> Anne
>  
> 
> -- 
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Anne Schilling]

Wait, isn't this the error I started with before I upgraded to OSX 10.12 
etc? I seem to be going in circles.
Is this related to https://trac.sagemath.org/ticket/17635 

?

Cheers,

Anne

On Tuesday, October 11, 2016 at 8:35:39 PM UTC-7, Anne Schilling wrote:
>
> Hi John,
>
> Thank you for the answer! I did what you suggested and this time, sage 
> started compiling and got to here:
>
> 
> [gf2x-1.1.p1] make[5]: Nothing to be done for `install-exec-am'.
> [gf2x-1.1.p1] make[5]: Nothing to be done for `install-data-am'.
> [gf2x-1.1.p1] Making install in src
> [gf2x-1.1.p1] make  install-am
> [gf2x-1.1.p1] make[6]: Nothing to be done for `install-exec-am'.
> [gf2x-1.1.p1] make[6]: Nothing to be done for `install-data-am'.
> [gf2x-1.1.p1] 
> [gf2x-1.1.p1] real4m35.653s
> [gf2x-1.1.p1] user4m21.480s
> [gf2x-1.1.p1] sys0m14.484s
> [gf2x-1.1.p1] Successfully installed gf2x-1.1.p1
> [gf2x-1.1.p1] Deleting temporary build directory
> [gf2x-1.1.p1] /Applications/sage/local/var/tmp/sage/build/gf2x-1.1.p1
> [gf2x-1.1.p1] Finished installing gf2x-1.1.p1.spkg
> make[1]: *** [all] Error 2
>
> real36m26.897s
> user95m0.211s
> sys12m51.527s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
>
> * package: givaro-4.0.2
>   log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
>   build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> make: *** [all] Error 1
>
> Any further ideas?
>
> Anne
>  
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Anne Schilling]

Hi John,

Thank you for the answer! I did what you suggested and this time, sage 
started compiling and got to here:


[gf2x-1.1.p1] make[5]: Nothing to be done for `install-exec-am'.
[gf2x-1.1.p1] make[5]: Nothing to be done for `install-data-am'.
[gf2x-1.1.p1] Making install in src
[gf2x-1.1.p1] make  install-am
[gf2x-1.1.p1] make[6]: Nothing to be done for `install-exec-am'.
[gf2x-1.1.p1] make[6]: Nothing to be done for `install-data-am'.
[gf2x-1.1.p1] 
[gf2x-1.1.p1] real4m35.653s
[gf2x-1.1.p1] user4m21.480s
[gf2x-1.1.p1] sys0m14.484s
[gf2x-1.1.p1] Successfully installed gf2x-1.1.p1
[gf2x-1.1.p1] Deleting temporary build directory
[gf2x-1.1.p1] /Applications/sage/local/var/tmp/sage/build/gf2x-1.1.p1
[gf2x-1.1.p1] Finished installing gf2x-1.1.p1.spkg
make[1]: *** [all] Error 2

real36m26.897s
user95m0.211s
sys12m51.527s
***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):

* package: givaro-4.0.2
  log file: /Applications/sage/logs/pkgs/givaro-4.0.2.log
  build directory: /Applications/sage/local/var/tmp/sage/build/givaro-4.0.2

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make: *** [all] Error 1

Any further ideas?

Anne
 

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Giving Sage AI-based step-by-step equation solving abilities

[rjf]

Nilsson's book was published in 1980.  I suspect that, even at that time, 
it was
considered as having a fairly limited perspective.

As far as PRESS is concerned, it would be possible to import it entirely
into SAGE  (assuming that PRESS is open source).  I believe there is an 
open implementation
of Prolog, apparently fairly efficient, in Lisp.  Since SAGE includes a 
complete
Lisp system, it could also include a complete Prolog system.
In fact, I doubt that many students do the kind of step-by-step analysis
outlined, but take much bigger steps after learning just a little.  What
they really do, I suspect, is study the examples in the text and study
the difference between the example and the problem.

This is partly an indictment of how math texts are written, and how math
is taught, and how students "learn" math --  realize that they do not want
to learn it necessarily.  Most of them just want to get credit for taking 
it.
(Not all of course, but lots of them.)


On Tuesday, October 11, 2016 at 2:16:58 PM UTC-7, William wrote:
>
> On Tue, Oct 11, 2016 at 1:15 PM, Ted Kosan  > wrote: 
> > Richard wrote: 
> > 
> >> I think that calling this Artificial Intelligence is probably unhelpful 
> and 
> >> arguably wrong. But maybe you (and maybe the PRESS people) are 
> >> calling rules + search + evaluation as AI? 
> > 
> > I am currently reading a book titled "Principles of Artificial 
> > Intelligence" by Nils J. Nilsson. Two of its nine chapters are devoted 
> > specifically to search, and most of the chapters discuss rules. 
> > According to Nilsson's Wikipedia page, he is one of the founding 
> > researchers in the field of artificial intelligence. I call my 
> > step-by-step equation solver Artificial Intelligence because 
> > everything I have read so far on classic AI indicates that is what it 
> > is. 
>
> The term "AI", especially in the 1990s, has a bad reputation among 
> some people, due to having massively over-promised and 
> under-delivered.  It  got hyped like crazy by both academics and 
> companies at certain points in the past.The term can -- in some 
> cases -- cause some people who have been paying attention to CS 
> research for a few decades (such as RJF) to cringe. 
>
> For what it is worth, in recent years, there is a field that's been 
> labeled "machine learning", (which is of course closely related to 
> statistics, AI, etc.).  The term "machine learning" is generally 
> viewed in a fairly positive light, since the practioners tends to make 
> more limited claims, and have had some impressive recent successes 
> (e.g., beating top human Go players, doing automatic language 
> translation, etc.). 
>
> My position: Ted, whatever you want to call it, many thanks for 
> sharing your work with us Sage devs.  It is really potentially very 
> valuable to possibly massively enlarge the range of people who might 
> use Sage.  We sage devs have done relatively little in quite some time 
> to enlarge the potential user base of Sage itself. 
>
> > 
> > Ted 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

On Tuesday, October 11, 2016 at 2:15:06 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, October 11, 2016 at 1:26:22 PM UTC-7, Dima Pasechnik wrote:
>>
>>
>>
>> On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
>>>
>>> Right, Sage's Python is broken. Try deleting sage/local/bin/python and 
>>> python2, and also sage/local/lib/python2.7 and 
>>> sage/local/lib/libpython2.7.dylib. Then the build process should use the 
>>> system's Python until Sage builds a working one.
>>>
>>
>> hmm, I don't understand. I think I tried starting from 'make distclean' 
>> and still got stuck at that  No module named _scproxy thing.
>>
>
> Are you saying you did this with the 'develop' branch or with the branch 
> from #21567? I can understand the former; that's why we have #21567.
>
> When we build Python on OS X, we should test that _scproxy builds 
> correctly before declaring the build a success.
>

See https://trac.sagemath.org/ticket/21685

 

>
>   John
>
>  
>
>>
>>  
>>
>
>>>
>>>
>>> On Tuesday, October 11, 2016 at 12:19:47 PM UTC-7, Anne Schilling wrote:

 Well, in fact now no matter what I do, I get this error. Even from the 
 master branch:

 make distclean
 make -j4 build/make/Makefile
 ./bootstrap -d
 rm -rf config configure build/make/Makefile-auto.in
 ./bootstrap: line 29: aclocal: command not found
 Bootstrap failed, downloading required files instead.
 Traceback (most recent call last):
   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
 
 from sage_bootstrap.download.cmdline import run_safe
   File 
 "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", 
 line 
 7, in 
 from sage_bootstrap.download.transfer import Download
   File 
 "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", 
 line 
 23, in 
 from sage_bootstrap.compat import urllib
   File 
 "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
 23, in 
 import urllib
   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
 
 from _scproxy import _get_proxy_settings, _get_proxies
 ImportError: No module named _scproxy
 Error: downloading configure-176.tar.gz failed
 make[1]: *** [configure] Error 1
 make: *** [build-clean] Error 2


 On Tuesday, October 11, 2016 at 12:10:32 PM UTC-7, Anne Schilling wrote:
>
> I guess I was overzealous upgrading to OSX10.12.
>
> Thanks John for your suggestions! With ticket 21567, I do not seem to 
> get very far:
>
> make
> make -j4 build/make/Makefile
> ./bootstrap -d
> rm -rf config configure build/make/Makefile-auto.in
> ./bootstrap: line 31: aclocal: command not found
> Bootstrap failed, downloading required files instead.
> Traceback (most recent call last):
>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
> 
> from sage_bootstrap.download.cmdline import run_safe
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", 
> line 
> 7, in 
> from sage_bootstrap.download.transfer import Download
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", 
> line 
> 23, in 
> from sage_bootstrap.compat import urllib
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
> 23, in 
> import urllib
>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
> 
> from _scproxy import _get_proxy_settings, _get_proxies
> ImportError: No module named _scproxy
> Error: downloading configure-183.tar.gz failed
> make[1]: *** [configure] Error 1
> make: *** [all] Error 2
>
> Best,
>
> Anne
>
>
> On Tuesday, October 11, 2016 at 11:50:30 AM UTC-7, John H Palmieri 
> wrote:
>>
>>
>>
>> On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling 
>> wrote:
>>>
>>> Hi Volker,
>>>
>>> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
>>> latest version command line xcode. Now I get the following
>>> error (even when compiling the latest stable release of sage):
>>>
>>
>> Volker actually suggested upgrading to OS X 10.11. Sage does not 
>> build out of the box on OS X 10.12 yet, but there is a branch at 
>> https://trac.sagemath.org/ticket/21567 which works for me. You may 
>> need to do "sage -f python2" to force it to reinstall Python, since on 
>> OS X 
>> 10.12, Sage fails to build Python correctly (although it thinks it has). 
>> So: (1) get the branch from #21567, (2) do "sage -f python2", and then 
>> "make", or (2') do "make distclean" followed by "make". And keep your 
>> fingers crossed.
>>
>>   John

Re: [sage-devel] Giving Sage AI-based step-by-step equation solving abilities

[William Stein]

On Tue, Oct 11, 2016 at 1:15 PM, Ted Kosan  wrote:
> Richard wrote:
>
>> I think that calling this Artificial Intelligence is probably unhelpful and
>> arguably wrong. But maybe you (and maybe the PRESS people) are
>> calling rules + search + evaluation as AI?
>
> I am currently reading a book titled "Principles of Artificial
> Intelligence" by Nils J. Nilsson. Two of its nine chapters are devoted
> specifically to search, and most of the chapters discuss rules.
> According to Nilsson's Wikipedia page, he is one of the founding
> researchers in the field of artificial intelligence. I call my
> step-by-step equation solver Artificial Intelligence because
> everything I have read so far on classic AI indicates that is what it
> is.

The term "AI", especially in the 1990s, has a bad reputation among
some people, due to having massively over-promised and
under-delivered.  It  got hyped like crazy by both academics and
companies at certain points in the past.The term can -- in some
cases -- cause some people who have been paying attention to CS
research for a few decades (such as RJF) to cringe.

For what it is worth, in recent years, there is a field that's been
labeled "machine learning", (which is of course closely related to
statistics, AI, etc.).  The term "machine learning" is generally
viewed in a fairly positive light, since the practioners tends to make
more limited claims, and have had some impressive recent successes
(e.g., beating top human Go players, doing automatic language
translation, etc.).

My position: Ted, whatever you want to call it, many thanks for
sharing your work with us Sage devs.  It is really potentially very
valuable to possibly massively enlarge the range of people who might
use Sage.  We sage devs have done relatively little in quite some time
to enlarge the potential user base of Sage itself.

>
> Ted
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

On Tuesday, October 11, 2016 at 1:26:22 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
>>
>> Right, Sage's Python is broken. Try deleting sage/local/bin/python and 
>> python2, and also sage/local/lib/python2.7 and 
>> sage/local/lib/libpython2.7.dylib. Then the build process should use the 
>> system's Python until Sage builds a working one.
>>
>
> hmm, I don't understand. I think I tried starting from 'make distclean' 
> and still got stuck at that  No module named _scproxy thing.
>

Are you saying you did this with the 'develop' branch or with the branch 
from #21567? I can understand the former; that's why we have #21567.

When we build Python on OS X, we should test that _scproxy builds correctly 
before declaring the build a success.

  John

 

>
>  
>

>>
>>
>> On Tuesday, October 11, 2016 at 12:19:47 PM UTC-7, Anne Schilling wrote:
>>>
>>> Well, in fact now no matter what I do, I get this error. Even from the 
>>> master branch:
>>>
>>> make distclean
>>> make -j4 build/make/Makefile
>>> ./bootstrap -d
>>> rm -rf config configure build/make/Makefile-auto.in
>>> ./bootstrap: line 29: aclocal: command not found
>>> Bootstrap failed, downloading required files instead.
>>> Traceback (most recent call last):
>>>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
>>> 
>>> from sage_bootstrap.download.cmdline import run_safe
>>>   File 
>>> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
>>> 7, in 
>>> from sage_bootstrap.download.transfer import Download
>>>   File 
>>> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
>>> 23, in 
>>> from sage_bootstrap.compat import urllib
>>>   File 
>>> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
>>> 23, in 
>>> import urllib
>>>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
>>> 
>>> from _scproxy import _get_proxy_settings, _get_proxies
>>> ImportError: No module named _scproxy
>>> Error: downloading configure-176.tar.gz failed
>>> make[1]: *** [configure] Error 1
>>> make: *** [build-clean] Error 2
>>>
>>>
>>> On Tuesday, October 11, 2016 at 12:10:32 PM UTC-7, Anne Schilling wrote:

 I guess I was overzealous upgrading to OSX10.12.

 Thanks John for your suggestions! With ticket 21567, I do not seem to 
 get very far:

 make
 make -j4 build/make/Makefile
 ./bootstrap -d
 rm -rf config configure build/make/Makefile-auto.in
 ./bootstrap: line 31: aclocal: command not found
 Bootstrap failed, downloading required files instead.
 Traceback (most recent call last):
   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
 
 from sage_bootstrap.download.cmdline import run_safe
   File 
 "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", 
 line 
 7, in 
 from sage_bootstrap.download.transfer import Download
   File 
 "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", 
 line 
 23, in 
 from sage_bootstrap.compat import urllib
   File 
 "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
 23, in 
 import urllib
   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
 
 from _scproxy import _get_proxy_settings, _get_proxies
 ImportError: No module named _scproxy
 Error: downloading configure-183.tar.gz failed
 make[1]: *** [configure] Error 1
 make: *** [all] Error 2

 Best,

 Anne


 On Tuesday, October 11, 2016 at 11:50:30 AM UTC-7, John H Palmieri 
 wrote:
>
>
>
> On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling 
> wrote:
>>
>> Hi Volker,
>>
>> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
>> latest version command line xcode. Now I get the following
>> error (even when compiling the latest stable release of sage):
>>
>
> Volker actually suggested upgrading to OS X 10.11. Sage does not build 
> out of the box on OS X 10.12 yet, but there is a branch at 
> https://trac.sagemath.org/ticket/21567 which works for me. You may 
> need to do "sage -f python2" to force it to reinstall Python, since on OS 
> X 
> 10.12, Sage fails to build Python correctly (although it thinks it has). 
> So: (1) get the branch from #21567, (2) do "sage -f python2", and then 
> "make", or (2') do "make distclean" followed by "make". And keep your 
> fingers crossed.
>
>   John
>
>  
>
>>
>> ...
>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
>> ./z_transform/rtest_z_transform.mac 
>> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 19:05, Kwankyu Lee wrote:

I stopped hades. Is the fault with the patchbot, not with Sage 7.4.rc0?


No idea, I don't know the cause of the problem on hades.

--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 17:56, John Cremona wrote:

I will do that -- but I have never done anything other than follow
those instructions, and never knowking started running the patchbot
inside a Sage shell!


I never said it was your fault. It could very well be that the issue was 
in the implementation or the instructions.


--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 20:34, Frédéric Chapoton wrote:

I now have this problem on my own machine:

sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' already
defined

and this has nothing to do with any patchbot..


Since you seem to be the only one having this problem, you need to give 
more details...


In particular, I need to see the log file
logs/pkgs/cython-0.24.1.p2.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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 19:04, Frédéric Chapoton wrote:

if you look here, you see that almost all bots have failed to build 7.4.rc0:

https://patchbot.sagemath.org/ticket/0/


Some of these are temporary problems due to #21672. You will see that 
arando for example managed to build some tickets successfully.


--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[François Bissey]

On 12/10/16 09:26, Dima Pasechnik wrote:



On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:

Right, Sage's Python is broken. Try deleting sage/local/bin/python
and python2, and also sage/local/lib/python2.7 and
sage/local/lib/libpython2.7.dylib. Then the build process should use
the system's Python until Sage builds a working one.


hmm, I don't understand. I think I tried starting from 'make distclean'
and still got stuck at that  No module named _scproxy thing.


I know there are safe guards in sage-env but nonetheless once the broken
python is installed it has to be cleaned manually. It is my experience 
too. It is an OS X (mainly Sierra right now) thing only.


Francois

--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Dima Pasechnik]

On Tuesday, October 11, 2016 at 7:47:47 PM UTC, John H Palmieri wrote:
>
> Right, Sage's Python is broken. Try deleting sage/local/bin/python and 
> python2, and also sage/local/lib/python2.7 and 
> sage/local/lib/libpython2.7.dylib. Then the build process should use the 
> system's Python until Sage builds a working one.
>

hmm, I don't understand. I think I tried starting from 'make distclean' and 
still got stuck at that  No module named _scproxy thing.

>
>
>
> On Tuesday, October 11, 2016 at 12:19:47 PM UTC-7, Anne Schilling wrote:
>>
>> Well, in fact now no matter what I do, I get this error. Even from the 
>> master branch:
>>
>> make distclean
>> make -j4 build/make/Makefile
>> ./bootstrap -d
>> rm -rf config configure build/make/Makefile-auto.in
>> ./bootstrap: line 29: aclocal: command not found
>> Bootstrap failed, downloading required files instead.
>> Traceback (most recent call last):
>>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
>> 
>> from sage_bootstrap.download.cmdline import run_safe
>>   File 
>> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
>> 7, in 
>> from sage_bootstrap.download.transfer import Download
>>   File 
>> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
>> 23, in 
>> from sage_bootstrap.compat import urllib
>>   File 
>> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
>> 23, in 
>> import urllib
>>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
>> 
>> from _scproxy import _get_proxy_settings, _get_proxies
>> ImportError: No module named _scproxy
>> Error: downloading configure-176.tar.gz failed
>> make[1]: *** [configure] Error 1
>> make: *** [build-clean] Error 2
>>
>>
>> On Tuesday, October 11, 2016 at 12:10:32 PM UTC-7, Anne Schilling wrote:
>>>
>>> I guess I was overzealous upgrading to OSX10.12.
>>>
>>> Thanks John for your suggestions! With ticket 21567, I do not seem to 
>>> get very far:
>>>
>>> make
>>> make -j4 build/make/Makefile
>>> ./bootstrap -d
>>> rm -rf config configure build/make/Makefile-auto.in
>>> ./bootstrap: line 31: aclocal: command not found
>>> Bootstrap failed, downloading required files instead.
>>> Traceback (most recent call last):
>>>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
>>> 
>>> from sage_bootstrap.download.cmdline import run_safe
>>>   File 
>>> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
>>> 7, in 
>>> from sage_bootstrap.download.transfer import Download
>>>   File 
>>> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
>>> 23, in 
>>> from sage_bootstrap.compat import urllib
>>>   File 
>>> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
>>> 23, in 
>>> import urllib
>>>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
>>> 
>>> from _scproxy import _get_proxy_settings, _get_proxies
>>> ImportError: No module named _scproxy
>>> Error: downloading configure-183.tar.gz failed
>>> make[1]: *** [configure] Error 1
>>> make: *** [all] Error 2
>>>
>>> Best,
>>>
>>> Anne
>>>
>>>
>>> On Tuesday, October 11, 2016 at 11:50:30 AM UTC-7, John H Palmieri wrote:



 On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling wrote:
>
> Hi Volker,
>
> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
> latest version command line xcode. Now I get the following
> error (even when compiling the latest stable release of sage):
>

 Volker actually suggested upgrading to OS X 10.11. Sage does not build 
 out of the box on OS X 10.12 yet, but there is a branch at 
 https://trac.sagemath.org/ticket/21567 which works for me. You may 
 need to do "sage -f python2" to force it to reinstall Python, since on OS 
 X 
 10.12, Sage fails to build Python correctly (although it thinks it has). 
 So: (1) get the branch from #21567, (2) do "sage -f python2", and then 
 "make", or (2') do "make distclean" followed by "make". And keep your 
 fingers crossed.

   John

  

>
> ...
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
> ./z_transform/rtest_z_transform.mac 
> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
> ./z_transform/z_transform.mac 
> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
> [maxima-5.35.1.p2] Making install in demo
> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh
>  
> -d 
> [maxima-5.35.1.p2] test -z 
> "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c 
> -d 

Re: [sage-devel] Giving Sage AI-based step-by-step equation solving abilities

[Ted Kosan]

Richard wrote:

> I think that calling this Artificial Intelligence is probably unhelpful and
> arguably wrong. But maybe you (and maybe the PRESS people) are
> calling rules + search + evaluation as AI?

I am currently reading a book titled "Principles of Artificial
Intelligence" by Nils J. Nilsson. Two of its nine chapters are devoted
specifically to search, and most of the chapters discuss rules.
According to Nilsson's Wikipedia page, he is one of the founding
researchers in the field of artificial intelligence. I call my
step-by-step equation solver Artificial Intelligence because
everything I have read so far on classic AI indicates that is what it
is.

Ted

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[John H Palmieri]

Right, Sage's Python is broken. Try deleting sage/local/bin/python and 
python2, and also sage/local/lib/python2.7 and 
sage/local/lib/libpython2.7.dylib. Then the build process should use the 
system's Python until Sage builds a working one.



On Tuesday, October 11, 2016 at 12:19:47 PM UTC-7, Anne Schilling wrote:
>
> Well, in fact now no matter what I do, I get this error. Even from the 
> master branch:
>
> make distclean
> make -j4 build/make/Makefile
> ./bootstrap -d
> rm -rf config configure build/make/Makefile-auto.in
> ./bootstrap: line 29: aclocal: command not found
> Bootstrap failed, downloading required files instead.
> Traceback (most recent call last):
>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
> 
> from sage_bootstrap.download.cmdline import run_safe
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
> 7, in 
> from sage_bootstrap.download.transfer import Download
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
> 23, in 
> from sage_bootstrap.compat import urllib
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
> 23, in 
> import urllib
>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
> 
> from _scproxy import _get_proxy_settings, _get_proxies
> ImportError: No module named _scproxy
> Error: downloading configure-176.tar.gz failed
> make[1]: *** [configure] Error 1
> make: *** [build-clean] Error 2
>
>
> On Tuesday, October 11, 2016 at 12:10:32 PM UTC-7, Anne Schilling wrote:
>>
>> I guess I was overzealous upgrading to OSX10.12.
>>
>> Thanks John for your suggestions! With ticket 21567, I do not seem to get 
>> very far:
>>
>> make
>> make -j4 build/make/Makefile
>> ./bootstrap -d
>> rm -rf config configure build/make/Makefile-auto.in
>> ./bootstrap: line 31: aclocal: command not found
>> Bootstrap failed, downloading required files instead.
>> Traceback (most recent call last):
>>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
>> 
>> from sage_bootstrap.download.cmdline import run_safe
>>   File 
>> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
>> 7, in 
>> from sage_bootstrap.download.transfer import Download
>>   File 
>> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
>> 23, in 
>> from sage_bootstrap.compat import urllib
>>   File 
>> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
>> 23, in 
>> import urllib
>>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
>> 
>> from _scproxy import _get_proxy_settings, _get_proxies
>> ImportError: No module named _scproxy
>> Error: downloading configure-183.tar.gz failed
>> make[1]: *** [configure] Error 1
>> make: *** [all] Error 2
>>
>> Best,
>>
>> Anne
>>
>>
>> On Tuesday, October 11, 2016 at 11:50:30 AM UTC-7, John H Palmieri wrote:
>>>
>>>
>>>
>>> On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling wrote:

 Hi Volker,

 Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
 latest version command line xcode. Now I get the following
 error (even when compiling the latest stable release of sage):

>>>
>>> Volker actually suggested upgrading to OS X 10.11. Sage does not build 
>>> out of the box on OS X 10.12 yet, but there is a branch at 
>>> https://trac.sagemath.org/ticket/21567 which works for me. You may need 
>>> to do "sage -f python2" to force it to reinstall Python, since on OS X 
>>> 10.12, Sage fails to build Python correctly (although it thinks it has). 
>>> So: (1) get the branch from #21567, (2) do "sage -f python2", and then 
>>> "make", or (2') do "make distclean" followed by "make". And keep your 
>>> fingers crossed.
>>>
>>>   John
>>>
>>>  
>>>

 ...
 [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
 ./z_transform/rtest_z_transform.mac 
 /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
 [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
 ./z_transform/z_transform.mac 
 /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
 [maxima-5.35.1.p2] Making install in demo
 [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
 [maxima-5.35.1.p2] /bin/sh 
 /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh
  
 -d 
 [maxima-5.35.1.p2] test -z 
 "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c 
 -d "/Applications/sage/local/share/maxima/5.35.1/demo"
 [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 cf.dem demo.dem 
 eaton1.dem eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem 
 romberg.dem sumcon.dem trgsmp.dem manual.demo plots.mac 
 '/Applications/sage/local/share/maxima/5.35.1/demo'
 [maxima-5.35.1.p2] Making install 

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

[Anne Schilling]

Well, in fact now no matter what I do, I get this error. Even from the 
master branch:

make distclean
make -j4 build/make/Makefile
./bootstrap -d
rm -rf config configure build/make/Makefile-auto.in
./bootstrap: line 29: aclocal: command not found
Bootstrap failed, downloading required files instead.
Traceback (most recent call last):
  File "/Applications/sage/build/bin/sage-download-file", line 27, in 

from sage_bootstrap.download.cmdline import run_safe
  File 
"/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
7, in 
from sage_bootstrap.download.transfer import Download
  File 
"/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
23, in 
from sage_bootstrap.compat import urllib
  File "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", 
line 23, in 
import urllib
  File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 

from _scproxy import _get_proxy_settings, _get_proxies
ImportError: No module named _scproxy
Error: downloading configure-176.tar.gz failed
make[1]: *** [configure] Error 1
make: *** [build-clean] Error 2


On Tuesday, October 11, 2016 at 12:10:32 PM UTC-7, Anne Schilling wrote:
>
> I guess I was overzealous upgrading to OSX10.12.
>
> Thanks John for your suggestions! With ticket 21567, I do not seem to get 
> very far:
>
> make
> make -j4 build/make/Makefile
> ./bootstrap -d
> rm -rf config configure build/make/Makefile-auto.in
> ./bootstrap: line 31: aclocal: command not found
> Bootstrap failed, downloading required files instead.
> Traceback (most recent call last):
>   File "/Applications/sage/build/bin/sage-download-file", line 27, in 
> 
> from sage_bootstrap.download.cmdline import run_safe
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
> 7, in 
> from sage_bootstrap.download.transfer import Download
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
> 23, in 
> from sage_bootstrap.compat import urllib
>   File 
> "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", line 
> 23, in 
> import urllib
>   File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 
> 
> from _scproxy import _get_proxy_settings, _get_proxies
> ImportError: No module named _scproxy
> Error: downloading configure-183.tar.gz failed
> make[1]: *** [configure] Error 1
> make: *** [all] Error 2
>
> Best,
>
> Anne
>
>
> On Tuesday, October 11, 2016 at 11:50:30 AM UTC-7, John H Palmieri wrote:
>>
>>
>>
>> On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling wrote:
>>>
>>> Hi Volker,
>>>
>>> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
>>> latest version command line xcode. Now I get the following
>>> error (even when compiling the latest stable release of sage):
>>>
>>
>> Volker actually suggested upgrading to OS X 10.11. Sage does not build 
>> out of the box on OS X 10.12 yet, but there is a branch at 
>> https://trac.sagemath.org/ticket/21567 which works for me. You may need 
>> to do "sage -f python2" to force it to reinstall Python, since on OS X 
>> 10.12, Sage fails to build Python correctly (although it thinks it has). 
>> So: (1) get the branch from #21567, (2) do "sage -f python2", and then 
>> "make", or (2') do "make distclean" followed by "make". And keep your 
>> fingers crossed.
>>
>>   John
>>
>>  
>>
>>>
>>> ...
>>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
>>> ./z_transform/rtest_z_transform.mac 
>>> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
>>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
>>> ./z_transform/z_transform.mac 
>>> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
>>> [maxima-5.35.1.p2] Making install in demo
>>> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
>>> [maxima-5.35.1.p2] /bin/sh 
>>> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
>>> -d 
>>> [maxima-5.35.1.p2] test -z 
>>> "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c 
>>> -d "/Applications/sage/local/share/maxima/5.35.1/demo"
>>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 cf.dem demo.dem 
>>> eaton1.dem eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem 
>>> romberg.dem sumcon.dem trgsmp.dem manual.demo plots.mac 
>>> '/Applications/sage/local/share/maxima/5.35.1/demo'
>>> [maxima-5.35.1.p2] Making install in plotting
>>> [maxima-5.35.1.p2] test -z 
>>> "/Applications/sage/local/libexec/maxima/5.35.1" || .././install-sh -c -d 
>>> "/Applications/sage/local/libexec/maxima/5.35.1"
>>> [maxima-5.35.1.p2] /bin/sh 
>>> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
>>> -d 
>>> [maxima-5.35.1.p2]  /usr/bin/install -c mgnuplot 
>>> '/Applications/sage/local/libexec/maxima/5.35.1'
>>> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
>>> 

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

[Anne Schilling]

I guess I was overzealous upgrading to OSX10.12.

Thanks John for your suggestions! With ticket 21567, I do not seem to get 
very far:

make
make -j4 build/make/Makefile
./bootstrap -d
rm -rf config configure build/make/Makefile-auto.in
./bootstrap: line 31: aclocal: command not found
Bootstrap failed, downloading required files instead.
Traceback (most recent call last):
  File "/Applications/sage/build/bin/sage-download-file", line 27, in 

from sage_bootstrap.download.cmdline import run_safe
  File 
"/Applications/sage/build/bin/../sage_bootstrap/download/__init__.py", line 
7, in 
from sage_bootstrap.download.transfer import Download
  File 
"/Applications/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
23, in 
from sage_bootstrap.compat import urllib
  File "/Applications/sage/build/bin/../sage_bootstrap/compat/__init__.py", 
line 23, in 
import urllib
  File "/Applications/sage/local/lib/python/urllib.py", line 1414, in 

from _scproxy import _get_proxy_settings, _get_proxies
ImportError: No module named _scproxy
Error: downloading configure-183.tar.gz failed
make[1]: *** [configure] Error 1
make: *** [all] Error 2

Best,

Anne


On Tuesday, October 11, 2016 at 11:50:30 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling wrote:
>>
>> Hi Volker,
>>
>> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
>> latest version command line xcode. Now I get the following
>> error (even when compiling the latest stable release of sage):
>>
>
> Volker actually suggested upgrading to OS X 10.11. Sage does not build out 
> of the box on OS X 10.12 yet, but there is a branch at 
> https://trac.sagemath.org/ticket/21567 which works for me. You may need 
> to do "sage -f python2" to force it to reinstall Python, since on OS X 
> 10.12, Sage fails to build Python correctly (although it thinks it has). 
> So: (1) get the branch from #21567, (2) do "sage -f python2", and then 
> "make", or (2') do "make distclean" followed by "make". And keep your 
> fingers crossed.
>
>   John
>
>  
>
>>
>> ...
>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
>> ./z_transform/rtest_z_transform.mac 
>> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
>> ./z_transform/z_transform.mac 
>> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
>> [maxima-5.35.1.p2] Making install in demo
>> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
>> [maxima-5.35.1.p2] /bin/sh 
>> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
>> -d 
>> [maxima-5.35.1.p2] test -z 
>> "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c 
>> -d "/Applications/sage/local/share/maxima/5.35.1/demo"
>> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 cf.dem demo.dem eaton1.dem 
>> eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem romberg.dem 
>> sumcon.dem trgsmp.dem manual.demo plots.mac 
>> '/Applications/sage/local/share/maxima/5.35.1/demo'
>> [maxima-5.35.1.p2] Making install in plotting
>> [maxima-5.35.1.p2] test -z 
>> "/Applications/sage/local/libexec/maxima/5.35.1" || .././install-sh -c -d 
>> "/Applications/sage/local/libexec/maxima/5.35.1"
>> [maxima-5.35.1.p2] /bin/sh 
>> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
>> -d 
>> [maxima-5.35.1.p2]  /usr/bin/install -c mgnuplot 
>> '/Applications/sage/local/libexec/maxima/5.35.1'
>> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
>> [maxima-5.35.1.p2] /bin/sh 
>> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
>> -d 
>> [maxima-5.35.1.p2] 
>> [maxima-5.35.1.p2] Now installing the Maxima library as 
>> '/Applications/sage/local/lib/ecl//maxima.fas'...
>> [maxima-5.35.1.p2] 
>> [maxima-5.35.1.p2] real5m29.945s
>> [maxima-5.35.1.p2] user4m48.551s
>> [maxima-5.35.1.p2] sys0m36.527s
>> [maxima-5.35.1.p2] Successfully installed maxima-5.35.1.p2
>> [maxima-5.35.1.p2] Deleting temporary build directory
>> [maxima-5.35.1.p2] 
>> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2
>> [maxima-5.35.1.p2] Finished installing maxima-5.35.1.p2.spkg
>> make[1]: *** [all] Error 2
>>
>> real49m54.858s
>> user145m38.154s
>> sys18m47.495s
>> ***
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all'):
>>
>> The build directory may contain configuration files and other potentially
>> helpful information. WARNING: if you now run 'make' again, the build
>> directory will, by default, be deleted. Set the environment variable
>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>
>> make: *** [all] Error 1
>>
>>
>> Any further suggestions?
>>
>> Anne
>>
>> On Saturday, October 1, 2016 at 

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

[John H Palmieri]

On Tuesday, October 11, 2016 at 11:35:18 AM UTC-7, Anne Schilling wrote:
>
> Hi Volker,
>
> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the 
> latest version command line xcode. Now I get the following
> error (even when compiling the latest stable release of sage):
>

Volker actually suggested upgrading to OS X 10.11. Sage does not build out 
of the box on OS X 10.12 yet, but there is a branch at 
https://trac.sagemath.org/ticket/21567 which works for me. You may need to 
do "sage -f python2" to force it to reinstall Python, since on OS X 10.12, 
Sage fails to build Python correctly (although it thinks it has). So: (1) 
get the branch from #21567, (2) do "sage -f python2", and then "make", or 
(2') do "make distclean" followed by "make". And keep your fingers crossed.

  John

 

>
> ...
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
> ./z_transform/rtest_z_transform.mac 
> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
> ./z_transform/z_transform.mac 
> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
> [maxima-5.35.1.p2] Making install in demo
> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
> -d 
> [maxima-5.35.1.p2] test -z 
> "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c 
> -d "/Applications/sage/local/share/maxima/5.35.1/demo"
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 cf.dem demo.dem eaton1.dem 
> eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem romberg.dem 
> sumcon.dem trgsmp.dem manual.demo plots.mac 
> '/Applications/sage/local/share/maxima/5.35.1/demo'
> [maxima-5.35.1.p2] Making install in plotting
> [maxima-5.35.1.p2] test -z 
> "/Applications/sage/local/libexec/maxima/5.35.1" || .././install-sh -c -d 
> "/Applications/sage/local/libexec/maxima/5.35.1"
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
> -d 
> [maxima-5.35.1.p2]  /usr/bin/install -c mgnuplot 
> '/Applications/sage/local/libexec/maxima/5.35.1'
> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
> -d 
> [maxima-5.35.1.p2] 
> [maxima-5.35.1.p2] Now installing the Maxima library as 
> '/Applications/sage/local/lib/ecl//maxima.fas'...
> [maxima-5.35.1.p2] 
> [maxima-5.35.1.p2] real5m29.945s
> [maxima-5.35.1.p2] user4m48.551s
> [maxima-5.35.1.p2] sys0m36.527s
> [maxima-5.35.1.p2] Successfully installed maxima-5.35.1.p2
> [maxima-5.35.1.p2] Deleting temporary build directory
> [maxima-5.35.1.p2] 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2
> [maxima-5.35.1.p2] Finished installing maxima-5.35.1.p2.spkg
> make[1]: *** [all] Error 2
>
> real49m54.858s
> user145m38.154s
> sys18m47.495s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> make: *** [all] Error 1
>
>
> Any further suggestions?
>
> Anne
>
> On Saturday, October 1, 2016 at 1:16:02 AM UTC-7, Volker Braun wrote:
>>
>> My suggestion would be to upgrade to xcode 10.11, and then to the newer 
>> xcode that is available on osx 10.11 only. That linker should then properly 
>> support AVX instructions. Thats also the only OS/compiler version that we 
>> have a buildbot for (or receives updates from Apple for that matter).
>>
>>
>>
>> On Saturday, October 1, 2016 at 5:20:43 AM UTC+2, Anne Schilling wrote:
>>>
>>> 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 
 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 '-march=native' (on OSX?) in the 
 past. 
 > 
 > Best, 
 > Travis 
 > 
 > 
 > -- 
 > 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 

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

[Francois Bissey]

I am surprised you got that far with Xcode 8.0!

see https://trac.sagemath.org/ticket/21567

François

> On 12/10/2016, at 07:35, Anne Schilling  wrote:
> 
> Hi Volker,
> 
> Thanks for the suggestion. I upgraded to OSX 10.12 and installed the latest 
> version command line xcode. Now I get the following
> error (even when compiling the latest stable release of sage):
> 
> ...
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
> ./z_transform/rtest_z_transform.mac 
> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 ./z_transform/z_transform.mac 
> /Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
> [maxima-5.35.1.p2] Making install in demo
> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
> -d 
> [maxima-5.35.1.p2] test -z 
> "/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c -d 
> "/Applications/sage/local/share/maxima/5.35.1/demo"
> [maxima-5.35.1.p2]  /usr/bin/install -c -m 644 cf.dem demo.dem eaton1.dem 
> eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem romberg.dem 
> sumcon.dem trgsmp.dem manual.demo plots.mac 
> '/Applications/sage/local/share/maxima/5.35.1/demo'
> [maxima-5.35.1.p2] Making install in plotting
> [maxima-5.35.1.p2] test -z "/Applications/sage/local/libexec/maxima/5.35.1" 
> || .././install-sh -c -d "/Applications/sage/local/libexec/maxima/5.35.1"
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
> -d 
> [maxima-5.35.1.p2]  /usr/bin/install -c mgnuplot 
> '/Applications/sage/local/libexec/maxima/5.35.1'
> [maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
> [maxima-5.35.1.p2] /bin/sh 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
> -d 
> [maxima-5.35.1.p2] 
> [maxima-5.35.1.p2] Now installing the Maxima library as 
> '/Applications/sage/local/lib/ecl//maxima.fas'...
> [maxima-5.35.1.p2] 
> [maxima-5.35.1.p2] real5m29.945s
> [maxima-5.35.1.p2] user4m48.551s
> [maxima-5.35.1.p2] sys0m36.527s
> [maxima-5.35.1.p2] Successfully installed maxima-5.35.1.p2
> [maxima-5.35.1.p2] Deleting temporary build directory
> [maxima-5.35.1.p2] 
> /Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2
> [maxima-5.35.1.p2] Finished installing maxima-5.35.1.p2.spkg
> make[1]: *** [all] Error 2
> 
> real49m54.858s
> user145m38.154s
> sys18m47.495s
> ***
> Error building Sage.
> 
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all'):
> 
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
> 
> make: *** [all] Error 1
> 
> 
> Any further suggestions?
> 
> Anne
> 
> On Saturday, October 1, 2016 at 1:16:02 AM UTC-7, Volker Braun wrote:
> My suggestion would be to upgrade to xcode 10.11, and then to the newer xcode 
> that is available on osx 10.11 only. That linker should then properly support 
> AVX instructions. Thats also the only OS/compiler version that we have a 
> buildbot for (or receives updates from Apple for that matter).
> 
> 
> 
> On Saturday, October 1, 2016 at 5:20:43 AM UTC+2, Anne Schilling wrote:
> 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 
> 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 '-march=native' (on OSX?) in the past. 
> > 
> > Best, 
> > Travis 
> > 
> > 
> > -- 
> > 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+...@googlegroups.com. 
> > To post to this group, send email to sage-...@googlegroups.com. 
> > Visit this group at https://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 

Re: [sage-devel] NTL v10

[Francois Bissey]

> On 12/10/2016, at 06:54, Victor Shoup  wrote:
> 
> While I'm not ready to go all autotools, I've started reading about it.
> I read about the DESTDIR trick that some package managers use,
> so I added support for that in the makefile.  Although I suppose 
> that may not be so relevant for Sage.
> 

Relevant to me! And certainly for the debian packagers too.

François

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Anne Schilling]

Hi Volker,

Thanks for the suggestion. I upgraded to OSX 10.12 and installed the latest 
version command line xcode. Now I get the following
error (even when compiling the latest stable release of sage):

...
[maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
./z_transform/rtest_z_transform.mac 
/Applications/sage/local/share/maxima/5.35.1/share/z_transform/rtest_z_transform.mac
[maxima-5.35.1.p2]  /usr/bin/install -c -m 644 
./z_transform/z_transform.mac 
/Applications/sage/local/share/maxima/5.35.1/share/z_transform/z_transform.mac
[maxima-5.35.1.p2] Making install in demo
[maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
[maxima-5.35.1.p2] /bin/sh 
/Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
-d 
[maxima-5.35.1.p2] test -z 
"/Applications/sage/local/share/maxima/5.35.1/demo" || .././install-sh -c 
-d "/Applications/sage/local/share/maxima/5.35.1/demo"
[maxima-5.35.1.p2]  /usr/bin/install -c -m 644 cf.dem demo.dem eaton1.dem 
eaton2.dem ezgcd.dem hypgeo.dem macex.dem macro.dem newfac.dem romberg.dem 
sumcon.dem trgsmp.dem manual.demo plots.mac 
'/Applications/sage/local/share/maxima/5.35.1/demo'
[maxima-5.35.1.p2] Making install in plotting
[maxima-5.35.1.p2] test -z "/Applications/sage/local/libexec/maxima/5.35.1" 
|| .././install-sh -c -d "/Applications/sage/local/libexec/maxima/5.35.1"
[maxima-5.35.1.p2] /bin/sh 
/Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
-d 
[maxima-5.35.1.p2]  /usr/bin/install -c mgnuplot 
'/Applications/sage/local/libexec/maxima/5.35.1'
[maxima-5.35.1.p2] make[5]: Nothing to be done for `install-exec-am'.
[maxima-5.35.1.p2] /bin/sh 
/Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2/src/install-sh 
-d 
[maxima-5.35.1.p2] 
[maxima-5.35.1.p2] Now installing the Maxima library as 
'/Applications/sage/local/lib/ecl//maxima.fas'...
[maxima-5.35.1.p2] 
[maxima-5.35.1.p2] real5m29.945s
[maxima-5.35.1.p2] user4m48.551s
[maxima-5.35.1.p2] sys0m36.527s
[maxima-5.35.1.p2] Successfully installed maxima-5.35.1.p2
[maxima-5.35.1.p2] Deleting temporary build directory
[maxima-5.35.1.p2] 
/Applications/sage/local/var/tmp/sage/build/maxima-5.35.1.p2
[maxima-5.35.1.p2] Finished installing maxima-5.35.1.p2.spkg
make[1]: *** [all] Error 2

real49m54.858s
user145m38.154s
sys18m47.495s
***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all'):

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make: *** [all] Error 1


Any further suggestions?

Anne

On Saturday, October 1, 2016 at 1:16:02 AM UTC-7, Volker Braun wrote:
>
> My suggestion would be to upgrade to xcode 10.11, and then to the newer 
> xcode that is available on osx 10.11 only. That linker should then properly 
> support AVX instructions. Thats also the only OS/compiler version that we 
> have a buildbot for (or receives updates from Apple for that matter).
>
>
>
> On Saturday, October 1, 2016 at 5:20:43 AM UTC+2, Anne Schilling wrote:
>>
>> 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 
>>> 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 '-march=native' (on OSX?) in the past. 
>>> > 
>>> > Best, 
>>> > Travis 
>>> > 
>>> > 
>>> > -- 
>>> > 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+...@googlegroups.com. 
>>> > To post to this group, send email to sage-...@googlegroups.com. 
>>> > Visit this group at https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Build issues with patchbots hades, poseidon and fermat

[Frédéric Chapoton]

I now have this problem on my own machine:

sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' already 
defined

and this has nothing to do with any patchbot..

Frederic

Le mardi 11 octobre 2016 19:04:40 UTC+2, Frédéric Chapoton a écrit :
>
> if you look here, you see that almost all bots have failed to build 
> 7.4.rc0:
>
> https://patchbot.sagemath.org/ticket/0/
>
> Among them is my own bot, now stopped. I tried a make distclean & make, 
> and the same error still appears.
>
> Frederic
>
> Le mardi 11 octobre 2016 09:38:19 UTC+2, Eric Gourgoulhon a écrit :
>>
>> Hi,
>>
>> Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the 
>> message:
>>
>> [openblas-0.2.19] ./openblas_utest: error while loading shared libraries: 
>> libgfortran.so.3: cannot open shared object file: No such file or directory
>>
>>
>> while fermat fails with the message:
>>
>> [sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: 
>> '_floordiv_' already defined
>> See for instance https://patchbot.sagemath.org/ticket/18843/
>>
>> 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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: NTL v10

[Victor Shoup]

Almost done with the new release!
I've taken care of the recursive make patch and both of the libtool patches.

While I'm not ready to go all autotools, I've started reading about it.
I read about the DESTDIR trick that some package managers use,
so I added support for that in the makefile.  Although I suppose 
that may not be so relevant for Sage.

I also added a few "recipes" that will allow you to skip the very slow
Wizard step, at least for a few typical platforms.

So now I'm working on updating the documentation, especially
the unix installation instructions, which were anyway in need of
some polishing.

I will hopefully release tomorrow!!

I'll continue reading about autotools.  NTL does a few quirky things during
the build process -- I have to see if all of that maps nicely into 
autotools world.
Some NTL source files may also need some minor updates, too.

BTW, I also remember using paper tape...but that was mainly just 
to backup my programs, if I recall correctly.  Ahhh...those were the days 
:-)

On Saturday, October 8, 2016 at 4:21:14 PM UTC-4, Victor Shoup wrote:
>
> I hope this is of some interest to the Sage community.
> I've just released a new version of NTL at http://www.shoup.net/ntl
>
> Here is a summary of changes.
>
> *New License: LGPLv2.1*
>
>- With the permission of all relevant contributors, NTL is now 
>licensed under  LGPLv2.1+ (the Lesser GNU Public License version 2.1 or 
>later).
>- Previously, NTL was licensed under the GPL. This new, less 
>restrictive licensing should hopefully increase the  impact of NTL.
>
>
> *Long integer package restructuring*
>
>- I've restructured the long integer package so that the GMP and 
>"classical LIP" modules share much of the same code base.
>- This greatly reduces the amount of redundant code, which will make 
>maintenance easier moving forward.
>- As a bonus, the classical LIP module is simpler, faster, and 
>(finally) thread safe. 
>- As another bonus, the GMP module now is much closer to being 
>compatible with "non-empty nails". Although it has not been tested in that 
>mode as of yet, it may eventually be helpful in the future if I want to 
>replace some GMP code with code that exploits AVX-512 IFMA instructions.
>- As a part of this transition, "make check" now includes much more 
>extensive "unit testing" of the long integer package.
>- Despite the drastic changes "under the hood", this restructuring 
>should not affect at all any  NTL client code that relies only on the 
>documented interface, including even the ancient legacy interfaces 
>pre-dating NTLv5a from 2000.
>
>
> *File name restructuring*
>
>- I've renamed all the ".c" files to ".cpp" files in the Unix 
>distribution. This seems to be more in line with common practice, and 
>should make it easier to work with compilers and other software 
> development 
>tools.
>
>
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] NTL v10

[Justin C. Walker]

On Oct 11, 2016, at 01:13 , John Cremona wrote:

> On 11 October 2016 at 01:03, Victor Shoup  wrote:
>> First, you are definitely wrong about punch cards. I started programming
>> with Fortran on punch cards in the 70s.
> 
> Punch cards?  They were a great  advance on paper tape which is what
> *I* started on.   To correct a typo in your program you had to  read
> the whole tape in, make the correction, and punch out a whole new
> tape!  Cards were so much easier as you could just replace one card.
> That was 1970 I think

Paper tape?  Man - if only I had that when I started.  *I* had to use lights 
and switches on the console to do I/O back then.  That was on a UNIVAC 1103A, 
if I recall correctly...that was in 1957.

When I advanced to punch cards, and handing in decks to get a run in, I would 
sometimes get the deck back with a pink slip on top saying "Caution: your deck 
may be out of order!".  I eventually discovered that the last 8 or so columns 
could be used to serialize the deck.  The sorter was my friend after that...

Just had to add to the confusion!  :-}

As you were...

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
---
I'm beginning to like the cut of his jibberish.
---



-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Kwankyu Lee]

>
>  I was only trying to help but if I cause problems to others I'll just not 
> bother. 
>

I stopped hades. Is the fault with the patchbot, not with Sage 7.4.rc0? 

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Build issues with patchbots hades, poseidon and fermat

[Frédéric Chapoton]

if you look here, you see that almost all bots have failed to build 7.4.rc0:

https://patchbot.sagemath.org/ticket/0/

Among them is my own bot, now stopped. I tried a make distclean & make, and 
the same error still appears.

Frederic

Le mardi 11 octobre 2016 09:38:19 UTC+2, Eric Gourgoulhon a écrit :
>
> Hi,
>
> Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the message:
>
> [openblas-0.2.19] ./openblas_utest: error while loading shared libraries: 
> libgfortran.so.3: cannot open shared object file: No such file or directory
>
>
> while fermat fails with the message:
>
> [sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: 
> '_floordiv_' already defined
> See for instance https://patchbot.sagemath.org/ticket/18843/
>
> 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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[John Cremona]

On 11 October 2016 at 16:44, Jeroen Demeyer  wrote:
> On 2016-10-11 09:38, Eric Gourgoulhon wrote:
>>
>> [sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10:
>> '_floordiv_' already defined
>
>
> It seems that this machine is running the Sage patchbot within a Sage shell,
> which is not supported. Because of this, the environment variable
> PIP_INSTALL is set to a wrong value, so the fix from #21441 is not applied.
>
> In logs/install.log there is
>
> *** ALL ENVIRONMENT VARIABLES BEFORE BUILD: ***
> ...
> SAGE_ENV_SOURCED=4
> ...
>
> This shouldn't be there. Whether you are using the patchbot or not, you
> should not build Sage within a Sage shell.
>
> Concrete suggestions:
>
> 1. Stop this patchbot
>
> 2. Rebuild Python (./sage -f python2)
>
> 3. Run the patchbot properly, see https://wiki.sagemath.org/buildbot/details

I will do that -- but I have never done anything other than follow
those instructions, and never knowking started running the patchbot
inside a Sage shell!  I have had trouble stopping and restarting the
patchbot (I think I might have asked here about that but was not
helped by the replies).  When I stop it with Ctrl-C the current
directory (SAGE_ROOT) has the branch patchbot/base checked out.  I
don't know whether I should now go to a different branch before Step
2?

If this will take up more than epsilon of my time I'll just have to
stop the thing (I just did) and not restart it at all.  I was only
trying to help but if I cause problems to others I'll just not bother.

John

>
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 09:38, Eric Gourgoulhon wrote:

[sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' 
already defined


It seems that this machine is running the Sage patchbot within a Sage 
shell, which is not supported. Because of this, the environment variable 
PIP_INSTALL is set to a wrong value, so the fix from #21441 is not applied.


In logs/install.log there is

*** ALL ENVIRONMENT VARIABLES BEFORE BUILD: ***
...
SAGE_ENV_SOURCED=4
...

This shouldn't be there. Whether you are using the patchbot or not, you 
should not build Sage within a Sage shell.


Concrete suggestions:

1. Stop this patchbot

2. Rebuild Python (./sage -f python2)

3. Run the patchbot properly, see 
https://wiki.sagemath.org/buildbot/details


--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] NTL v10

[Dima Pasechnik]

On Tuesday, October 11, 2016 at 3:02:17 PM UTC, John Cremona wrote:
>
> On 11 October 2016 at 15:34, William Stein  
> wrote: 
> > On Tue, Oct 11, 2016 at 7:24 AM, Dima Pasechnik  > wrote: 
> >> 
> >> 
> >> On Tuesday, October 11, 2016 at 8:14:02 AM UTC, John Cremona wrote: 
> >>> 
> >>> On 11 October 2016 at 01:03, Victor Shoup  wrote: 
> >>> > First, you are definitely wrong about punch cards. I started 
> programming 
> >>> > with Fortran on punch cards in the 70s. 
> >>> 
> >>> Punch cards?  They were a great  advance on paper tape which is what 
> >>> *I* started on.   To correct a typo in your program you had to  read 
> >>> the whole tape in, make the correction, and punch out a whole new 
> >>> tape!  Cards were so much easier as you could just replace one card. 
> >> 
> >> 
> >> sure, I had this at some point (1981?) too; the OS was booted from a 
> big 
> >> roll of plastic tape, and files and stuff 
> >> were on paper tape... I don't recall whether it was Basic or Fortran 
> one had 
> >> to program it with... 
> > 
> > You guys were so lucky to have an actual computer! 
>
> I only had access to it on Sunday afternoons, in winter.  Most of the 
> year it was lifted (by crane) onto a ship because it belonged to 
> Cambridge U's department of geodesy and geophysics, and they used it 
> to map the ocean floor.  And the rest of the week when it was in 
> Cambridge the academics had it. 
>
> > 
> > I spent my first year or two programming in the 70s by using a book 
> > I found in the garbage combined with a computer-looking 
> > thing I built out of cardboard, and simulating everything 
> > on paper or in my head. 
>
>
in 1979, final year of high school, we programmed Turing machines, on paper.
I probably was way more clever that time, as I had hard time recalling how 
this work
when I had to mention this to a student few years ago :-)
 

> The rest of the week / year we worked on paper too!  (But I didn't 
> bother making a fake computer out of cardboard). 
>
> > 
> > Uphill both ways, in the snow. 
> > 
> >> 
> >>> 
> >>> That was 1970 I think 
> >>> 
> >>> > 
> >>> > Second, a complete transition to auto tools still feels like 
> overkill at 
> >>> > this point. 
> >>> > But I agree that it could come one day. 
> >>> 
> >>> With a lot of help (from people on this thread and for the same 
> >>> reasons) I went through that agony with eclib.  I don't regret it but 
> >>> I would not want to do it again! 
> >> 
> >> 
> >> I've done this for a couple of Sage packages (admittedly, smaller and 
> >> simpler than NTL)... 
> >> 
> >>> 
> >>> 
> >>> John 
> >>> 
> >>> > In any case, I am almost done with all the requested changes. 
> >>> > I will follow up with a couple of quick questions, though. 
> >>> > 
> >>> > 
> >>> > On Monday, October 10, 2016 at 5:09:48 PM UTC-4, Dima Pasechnik 
> wrote: 
> >>> >> 
> >>> >> 
> >>> >> 
> >>> >> On Monday, October 10, 2016 at 9:09:38 PM UTC+1, François wrote: 
> >>> >>> 
> >>> >>> On 11/10/16 01:58, Victor Shoup wrote: 
> >>> >>> > Another issue. I'm not sure if $(MAKE) is specific to gnu make 
> or if 
> >>> >>> > it 
> >>> >>> > is universal. 
> >>> >>> > In general, I don't want to assume gnu. But I can certainly make 
> >>> >>> > this 
> >>> >>> > the default, 
> >>> >>> > and provide a config variable to override. 
> >>> >>> 
> >>> >>> I'll have another go at this when you use 
> >>> >>> $(MAKE) inside a makefile you are making sure 
> >>> >>> that the make command used is the same one that 
> >>> >>> you called on the initial makefile. 
> >>> >>> 
> >>> >>> As other people mentioned it enable parallel make 
> >>> >>> to proceed nicely, and in the case where there is 
> >>> >>> several make command installed on the system 
> >>> >>> you avoid funny things happening. I have AIX 
> >>> >>> system which comes with its own posix make 
> >>> >>> command. Something like ntl probably require 
> >>> >>> gmake (GNU make), calling AIX make in the 
> >>> >>> middle is not a good idea. 
> >>> >>> 
> >>> >> 
> >>> >> Perhaps the most natural solution would be to change NTL build 
> system 
> >>> >> so 
> >>> >> that 
> >>> >> it uses the standard autotools chain (autoconf/automake etc), not 
> only 
> >>> >> libtool. 
> >>> >> Given that it uses very few external libraries, it ought to be an 
> easy 
> >>> >> task. 
> >>> >> 
> >>> >> Given that I am perhaps the only person in this thread who learned 
> to 
> >>> >> program using punch cards, 
> >>> >> I am a dinosaur from an earlier period, yet, I look into the future 
> :-) 
> >>> >> 
> >>> >> Dima 
> >>> >> 
> >>> >> 
> >>> >> 
> >>> >>> Francois 
> >>> > 
> >>> > -- 
> >>> > 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+...@googlegroups.com. 
> >>> > To post to this 

Re: [sage-devel] Giving Sage AI-based step-by-step equation solving abilities

[rjf]

I think that calling this Artificial Intelligence is probably unhelpful
and arguably wrong.
But maybe you (and maybe the PRESS people) are calling rules + search + 
evaluation
as AI?
  
Unless it has changed substantially from what I have seen in the
past,, PRESS is lacking in rigorous methods
for solving equations.  But then, maybe students are in the same
boat.


On Monday, October 10, 2016 at 8:15:21 AM UTC-7, tkosan wrote:
>
> Matthieu wrote: 
>
> > Is this solver works only for systems of linear equations ? 
>
> The solver I am writing is based on an AI program written in the 1970s 
> named PRESS (PRolog Equation Solving System), and PRESS was designed 
> to solve R Elementary equations, which can contain polynomial, 
> trigonometric, exponential and logarithmic functions. I have not 
> implemented all of PRESS's capabilities in my solver yet, but I am in 
> the process of doing so. 
>
> Ted 
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Eric Gourgoulhon]

Le mardi 11 octobre 2016 09:51:35 UTC+2, Jeroen Demeyer a écrit :
>
>
> It's annoying that only the patchbots have these errors, I have not seen 
> anybody else report them. 
>
>
A similar build error regarding fermat (sage/matrix/matrix0.pyx:4757:10: 
'_add_' already defined)
is here:
https://patchbot.sagemath.org/ticket/21454/

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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] NTL v10

[John Cremona]

On 11 October 2016 at 15:34, William Stein  wrote:
> On Tue, Oct 11, 2016 at 7:24 AM, Dima Pasechnik  wrote:
>>
>>
>> On Tuesday, October 11, 2016 at 8:14:02 AM UTC, John Cremona wrote:
>>>
>>> On 11 October 2016 at 01:03, Victor Shoup  wrote:
>>> > First, you are definitely wrong about punch cards. I started programming
>>> > with Fortran on punch cards in the 70s.
>>>
>>> Punch cards?  They were a great  advance on paper tape which is what
>>> *I* started on.   To correct a typo in your program you had to  read
>>> the whole tape in, make the correction, and punch out a whole new
>>> tape!  Cards were so much easier as you could just replace one card.
>>
>>
>> sure, I had this at some point (1981?) too; the OS was booted from a big
>> roll of plastic tape, and files and stuff
>> were on paper tape... I don't recall whether it was Basic or Fortran one had
>> to program it with...
>
> You guys were so lucky to have an actual computer!

I only had access to it on Sunday afternoons, in winter.  Most of the
year it was lifted (by crane) onto a ship because it belonged to
Cambridge U's department of geodesy and geophysics, and they used it
to map the ocean floor.  And the rest of the week when it was in
Cambridge the academics had it.

>
> I spent my first year or two programming in the 70s by using a book
> I found in the garbage combined with a computer-looking
> thing I built out of cardboard, and simulating everything
> on paper or in my head.

The rest of the week / year we worked on paper too!  (But I didn't
bother making a fake computer out of cardboard).

>
> Uphill both ways, in the snow.
>
>>
>>>
>>> That was 1970 I think
>>>
>>> >
>>> > Second, a complete transition to auto tools still feels like overkill at
>>> > this point.
>>> > But I agree that it could come one day.
>>>
>>> With a lot of help (from people on this thread and for the same
>>> reasons) I went through that agony with eclib.  I don't regret it but
>>> I would not want to do it again!
>>
>>
>> I've done this for a couple of Sage packages (admittedly, smaller and
>> simpler than NTL)...
>>
>>>
>>>
>>> John
>>>
>>> > In any case, I am almost done with all the requested changes.
>>> > I will follow up with a couple of quick questions, though.
>>> >
>>> >
>>> > On Monday, October 10, 2016 at 5:09:48 PM UTC-4, Dima Pasechnik wrote:
>>> >>
>>> >>
>>> >>
>>> >> On Monday, October 10, 2016 at 9:09:38 PM UTC+1, François wrote:
>>> >>>
>>> >>> On 11/10/16 01:58, Victor Shoup wrote:
>>> >>> > Another issue. I'm not sure if $(MAKE) is specific to gnu make or if
>>> >>> > it
>>> >>> > is universal.
>>> >>> > In general, I don't want to assume gnu. But I can certainly make
>>> >>> > this
>>> >>> > the default,
>>> >>> > and provide a config variable to override.
>>> >>>
>>> >>> I'll have another go at this when you use
>>> >>> $(MAKE) inside a makefile you are making sure
>>> >>> that the make command used is the same one that
>>> >>> you called on the initial makefile.
>>> >>>
>>> >>> As other people mentioned it enable parallel make
>>> >>> to proceed nicely, and in the case where there is
>>> >>> several make command installed on the system
>>> >>> you avoid funny things happening. I have AIX
>>> >>> system which comes with its own posix make
>>> >>> command. Something like ntl probably require
>>> >>> gmake (GNU make), calling AIX make in the
>>> >>> middle is not a good idea.
>>> >>>
>>> >>
>>> >> Perhaps the most natural solution would be to change NTL build system
>>> >> so
>>> >> that
>>> >> it uses the standard autotools chain (autoconf/automake etc), not only
>>> >> libtool.
>>> >> Given that it uses very few external libraries, it ought to be an easy
>>> >> task.
>>> >>
>>> >> Given that I am perhaps the only person in this thread who learned to
>>> >> program using punch cards,
>>> >> I am a dinosaur from an earlier period, yet, I look into the future :-)
>>> >>
>>> >> Dima
>>> >>
>>> >>
>>> >>
>>> >>> Francois
>>> >
>>> > --
>>> > 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+...@googlegroups.com.
>>> > To post to this group, send email to sage-...@googlegroups.com.
>>> > Visit this group at https://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 https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> William (http://wstein.org)
>
> --
> You received this message 

Re: [sage-devel] NTL v10

[William Stein]

On Tue, Oct 11, 2016 at 7:24 AM, Dima Pasechnik  wrote:
>
>
> On Tuesday, October 11, 2016 at 8:14:02 AM UTC, John Cremona wrote:
>>
>> On 11 October 2016 at 01:03, Victor Shoup  wrote:
>> > First, you are definitely wrong about punch cards. I started programming
>> > with Fortran on punch cards in the 70s.
>>
>> Punch cards?  They were a great  advance on paper tape which is what
>> *I* started on.   To correct a typo in your program you had to  read
>> the whole tape in, make the correction, and punch out a whole new
>> tape!  Cards were so much easier as you could just replace one card.
>
>
> sure, I had this at some point (1981?) too; the OS was booted from a big
> roll of plastic tape, and files and stuff
> were on paper tape... I don't recall whether it was Basic or Fortran one had
> to program it with...

You guys were so lucky to have an actual computer!

I spent my first year or two programming in the 70s by using a book
I found in the garbage combined with a computer-looking
thing I built out of cardboard, and simulating everything
on paper or in my head.

Uphill both ways, in the snow.

>
>>
>> That was 1970 I think
>>
>> >
>> > Second, a complete transition to auto tools still feels like overkill at
>> > this point.
>> > But I agree that it could come one day.
>>
>> With a lot of help (from people on this thread and for the same
>> reasons) I went through that agony with eclib.  I don't regret it but
>> I would not want to do it again!
>
>
> I've done this for a couple of Sage packages (admittedly, smaller and
> simpler than NTL)...
>
>>
>>
>> John
>>
>> > In any case, I am almost done with all the requested changes.
>> > I will follow up with a couple of quick questions, though.
>> >
>> >
>> > On Monday, October 10, 2016 at 5:09:48 PM UTC-4, Dima Pasechnik wrote:
>> >>
>> >>
>> >>
>> >> On Monday, October 10, 2016 at 9:09:38 PM UTC+1, François wrote:
>> >>>
>> >>> On 11/10/16 01:58, Victor Shoup wrote:
>> >>> > Another issue. I'm not sure if $(MAKE) is specific to gnu make or if
>> >>> > it
>> >>> > is universal.
>> >>> > In general, I don't want to assume gnu. But I can certainly make
>> >>> > this
>> >>> > the default,
>> >>> > and provide a config variable to override.
>> >>>
>> >>> I'll have another go at this when you use
>> >>> $(MAKE) inside a makefile you are making sure
>> >>> that the make command used is the same one that
>> >>> you called on the initial makefile.
>> >>>
>> >>> As other people mentioned it enable parallel make
>> >>> to proceed nicely, and in the case where there is
>> >>> several make command installed on the system
>> >>> you avoid funny things happening. I have AIX
>> >>> system which comes with its own posix make
>> >>> command. Something like ntl probably require
>> >>> gmake (GNU make), calling AIX make in the
>> >>> middle is not a good idea.
>> >>>
>> >>
>> >> Perhaps the most natural solution would be to change NTL build system
>> >> so
>> >> that
>> >> it uses the standard autotools chain (autoconf/automake etc), not only
>> >> libtool.
>> >> Given that it uses very few external libraries, it ought to be an easy
>> >> task.
>> >>
>> >> Given that I am perhaps the only person in this thread who learned to
>> >> program using punch cards,
>> >> I am a dinosaur from an earlier period, yet, I look into the future :-)
>> >>
>> >> Dima
>> >>
>> >>
>> >>
>> >>> Francois
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To post to this group, send email to sage-...@googlegroups.com.
>> > Visit this group at https://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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] NTL v10

[Dima Pasechnik]

On Tuesday, October 11, 2016 at 8:14:02 AM UTC, John Cremona wrote:
>
> On 11 October 2016 at 01:03, Victor Shoup  
> wrote: 
> > First, you are definitely wrong about punch cards. I started programming 
> > with Fortran on punch cards in the 70s. 
>
> Punch cards?  They were a great  advance on paper tape which is what 
> *I* started on.   To correct a typo in your program you had to  read 
> the whole tape in, make the correction, and punch out a whole new 
> tape!  Cards were so much easier as you could just replace one card. 
>

sure, I had this at some point (1981?) too; the OS was booted from a big 
roll of plastic tape, and files and stuff
were on paper tape... I don't recall whether it was Basic or Fortran one 
had to program it with...
 

> That was 1970 I think 
>
> > 
> > Second, a complete transition to auto tools still feels like overkill at 
> > this point. 
> > But I agree that it could come one day. 
>
> With a lot of help (from people on this thread and for the same 
> reasons) I went through that agony with eclib.  I don't regret it but 
> I would not want to do it again! 
>

I've done this for a couple of Sage packages (admittedly, smaller and 
simpler than NTL)...
 

>
> John 
>
> > In any case, I am almost done with all the requested changes. 
> > I will follow up with a couple of quick questions, though. 
> > 
> > 
> > On Monday, October 10, 2016 at 5:09:48 PM UTC-4, Dima Pasechnik wrote: 
> >> 
> >> 
> >> 
> >> On Monday, October 10, 2016 at 9:09:38 PM UTC+1, François wrote: 
> >>> 
> >>> On 11/10/16 01:58, Victor Shoup wrote: 
> >>> > Another issue. I'm not sure if $(MAKE) is specific to gnu make or if 
> it 
> >>> > is universal. 
> >>> > In general, I don't want to assume gnu. But I can certainly make 
> this 
> >>> > the default, 
> >>> > and provide a config variable to override. 
> >>> 
> >>> I'll have another go at this when you use 
> >>> $(MAKE) inside a makefile you are making sure 
> >>> that the make command used is the same one that 
> >>> you called on the initial makefile. 
> >>> 
> >>> As other people mentioned it enable parallel make 
> >>> to proceed nicely, and in the case where there is 
> >>> several make command installed on the system 
> >>> you avoid funny things happening. I have AIX 
> >>> system which comes with its own posix make 
> >>> command. Something like ntl probably require 
> >>> gmake (GNU make), calling AIX make in the 
> >>> middle is not a good idea. 
> >>> 
> >> 
> >> Perhaps the most natural solution would be to change NTL build system 
> so 
> >> that 
> >> it uses the standard autotools chain (autoconf/automake etc), not only 
> >> libtool. 
> >> Given that it uses very few external libraries, it ought to be an easy 
> >> task. 
> >> 
> >> Given that I am perhaps the only person in this thread who learned to 
> >> program using punch cards, 
> >> I am a dinosaur from an earlier period, yet, I look into the future :-) 
> >> 
> >> Dima 
> >> 
> >> 
> >> 
> >>> Francois 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Testing new graph algorithms

[Travis Scrimshaw]

>
>> Even if it does turn out that this technique performs worse than Sage on 
>> some graphs, is it worth trying to integrate it as an option for users?
>>
>
> Are these algorithms published? (sorry, "Mark Bell" isn't very googleable; 
> e.g. I found this https://arxiv.org/a/bell_m_3.html
> but this does not show any graph theory algorithms you mention :-))
> Surely, have more fast implementations of known algorithms is great; have 
> implementations of something
> unpublished, not so---indeed, code reviewers would try to check that the 
> implementation is implementing
> something published, but I don't think reviewing correctness of algorithms 
> is something one would reasonably expect from a 
> code review.
>
>
I think it is good to add it even if it is not published (although at least 
an (arXiv) preprint would be nice). In either case, IMO it would be good to 
have a way of choosing which algorithm to run in the methods, both for 
testing and verification purposes.

Best,
Travis

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: a 7(!) year old (Singular) overflow issue still holds

[Dima Pasechnik]

On Tuesday, October 11, 2016 at 4:47:23 AM UTC, Bill Hart wrote:
>
>
>
> On Monday, 10 October 2016 12:31:25 UTC+2, Dima Pasechnik wrote:
>>
>>
>>
>> On Sunday, October 9, 2016 at 4:48:31 PM UTC, Bill Hart wrote:
>>>
>>>
>>>
>>> On Sunday, 9 October 2016 18:08:29 UTC+2, Dima Pasechnik wrote:



 On Sunday, October 9, 2016 at 3:35:57 PM UTC, Bill Hart wrote:
>
> By default, Singular uses 16 bit exponents. But it is perfectly 
> capable of working with exponents up to 64 bits. That will be slower of 
> course.
>
> why? I presume arithmetic on 16-bit integers is not faster than on 
 32-bit, or even 64-bit.

>>>
>>> It's the exponent arithmetic, not the coefficients we are talking about.
>>>
>>  
>> sure - I was thinking about univariate case; in the multivariate case, if 
>> you want fast arithmetic on exponents of monomials given as integer vectors 
>> in year 2016, you probably would want to use GPU 
>>
>>
>>> The exponents are packed, with four 16 bit field in a 64 bit word. This 
>>> is *much* faster. I use the same trick, as does just about every decent 
>>> computer algebra system out there.
>>>
>>> Interestingly, Magma only allows exponents up to about 30 bits, but it 
>>> takes a few minutes to compute x^(2^30 - 1).
>>>
>>
>> I wonder why this happens - a Flint issue? :
>>
>> sage: R.=QQ[]
>> sage: x^(2^30)-1
>> Exception (FLINT memory_manager). Unable to allocate memory.
>>
>
> I'm not precisely sure why that happens. How much memory did you have 
> available on your machine?
>

16GB x86_64 Linux system, lightly loaded.
 

>
> This should create the polynomial x, then try to raise it to the power of 
> 2^30, which is about a billion I think.
>
> Along the way it will use the FFT, which is a bit of a memory hog.
>
> One day we ought to fix the powering code to handle monomials separately. 
> It is 2016 after all.
>

I imagine that, more generally, for the fewnomials (so that the monimials 
are  (almost) algebraically independent), it's faster to do "naive" 
powering, no? (i.e., the multinomial formula)

 

>
>
>> sage: x^(2^30-1)
>> Killed
>>
>> (which appears to indicate that the recovery from the exception was not 
>> complete)
>>
>> On the other hand:
>>
>> sage: timeit('x^(2^20-1)')
>> 125 loops, best of 3: 1.66 ms per loop
>> sage: 2^20-1
>> 1048575
>> sage: timeit('x^1048575')
>> 125 loops, best of 3: 1.66 ms per loop
>> sage: timeit('x^10')
>> 625 loops, best of 3: 381 ns per loop
>> sage: 2^30-1
>> 1073741823
>> sage: timeit('x^1073741823')
>> 5 loops, best of 3: 1.72 s per loop
>> sage: timeit('x^(2^30-1)')
>> 5 loops, best of 3: 1.71 s per loop
>>
>> but then
>>
>> sage: x^(2^30-1)
>>   
>> at 0x7fbb07bd7910>) failed: MemoryError>
>>
>>
> There's some caching in Flint I guess, though I'm not entirely sure why 
> that would matter here.
>
> Bill.
>  
>
>>
>>  looks quite  strange...
>> Dima
>>
>>  
>>>
  
  

> I guess it isn't easy for Sage to change the relevant ring upon 
> overflow to one using 64 bit exponents.
>
> I can't say whether it would be easy or hard for Singular to 
> automatically change the exponent size for you. For basic arithmetic, I 
> have implemented precisely this in the code I've been writing. But 
> Singular 
> is almost infinitely more complex than the very simple cases I've been 
> dealing with in my own code. At this stage I couldn't even hazard a guess.
>
> I'll ask Hans if I remember. But either way, I believe this would be 
> an *extremely* time consuming thing to fix. How important is it?
>
> Bill.
>
> On Wednesday, 5 October 2016 01:10:31 UTC+2, Jakob Kroeker wrote:
>>
>>
>> https://trac.sagemath.org/ticket/6472
>>
>> even for recent singular upgrade 
>>
>> https://trac.sagemath.org/ticket/17254
>>
>> and it was not(?) reported to upstream...
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Testing new graph algorithms

[Dima Pasechnik]

On Tuesday, October 11, 2016 at 11:25:09 AM UTC, Mark Bell wrote:
>
> I've been working on some new algorithms for computing some properties 
> (eccentricity, diameter, radius, ...) of (undirected) graphs and I'm 
> looking for families to test these on.
>
> I've written a reasonable efficient C extension which implements these 
> algorithms and so I've started comparing these against the methods 
> available in Sage.
> For many of the graphs that I've tried it appears that this new technique 
> is faster than Sage. For example, experimentally on:
>
> > G = graphs.RandomGNP(2001, 0.05)
>
> this new technique computes the diameter of G ~30% faster than Sage.
>
>
> Is there a standard test suite of graphs that I try running these 
> procedures on? I think this algorithm should be particularly effective on 
> graphs with a large number of vertices and a large diameter. Is there a 
> reasonable way of generating graphs of this form?
>

Some "large" graphs of "large" diameter that Sage knows about are distance 
regular, e.g.
graphs.SymplecticDualPolarGraph
It's hard to say more without knowing what exactly you're after, what kind 
of edge density, what kind of diameter as a function of the number of 
vertices, etc. 

>
> Even if it does turn out that this technique performs worse than Sage on 
> some graphs, is it worth trying to integrate it as an option for users?
>

Are these algorithms published? (sorry, "Mark Bell" isn't very googleable; 
e.g. I found this https://arxiv.org/a/bell_m_3.html
but this does not show any graph theory algorithms you mention :-))
Surely, have more fast implementations of known algorithms is great; have 
implementations of something
unpublished, not so---indeed, code reviewers would try to check that the 
implementation is implementing
something published, but I don't think reviewing correctness of algorithms 
is something one would reasonably expect from a 
code review.

Cheers,
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Testing new graph algorithms

['Mark Bell' via sage-devel]

I've been working on some new algorithms for computing some properties 
(eccentricity, diameter, radius, ...) of (undirected) graphs and I'm 
looking for families to test these on.

I've written a reasonable efficient C extension which implements these 
algorithms and so I've started comparing these against the methods 
available in Sage.
For many of the graphs that I've tried it appears that this new technique 
is faster than Sage. For example, experimentally on:

> G = graphs.RandomGNP(2001, 0.05)

this new technique computes the diameter of G ~30% faster than Sage.


Is there a standard test suite of graphs that I try running these 
procedures on? I think this algorithm should be particularly effective on 
graphs with a large number of vertices and a large diameter. Is there a 
reasonable way of generating graphs of this form?


Even if it does turn out that this technique performs worse than Sage on 
some graphs, is it worth trying to integrate it as an option for users?

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[John Cremona]

deme...@fermat.warwick.ac.uk

The machine had a new ubuntu o/s installed from scratch a month or so
ago so may not have all that's needed but has been running thepatch
bot for several weeks.

John

On 11 October 2016 at 09:42, Jeroen Demeyer  wrote:
> On 2016-10-11 10:14, John Cremona wrote:
>>
>> That's me, send me your ssh key.
>
>
> Here it is. Remember to give me the login details.
>
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 10:14, John Cremona wrote:

That's me, send me your ssh key.


Here it is. Remember to give me the login details.

--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


id_rsa.pub
Description: MS-Publisher document

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[John Cremona]

On 11 October 2016 at 08:45, Jeroen Demeyer  wrote:
> On 2016-10-11 09:38, Eric Gourgoulhon wrote:
>>
>> [sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10:
>> '_floordiv_' already defined
>
>
> This looks like a typical error which was fixed by #21441. However, that
> ticket is merged, so I don't have an explanation.
>
> If someone can give me access to this "fermat" machine, I could try to debug
> it.

That's me, send me your ssh key.

John

>
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] NTL v10

[John Cremona]

On 11 October 2016 at 01:03, Victor Shoup  wrote:
> First, you are definitely wrong about punch cards. I started programming
> with Fortran on punch cards in the 70s.

Punch cards?  They were a great  advance on paper tape which is what
*I* started on.   To correct a typo in your program you had to  read
the whole tape in, make the correction, and punch out a whole new
tape!  Cards were so much easier as you could just replace one card.
That was 1970 I think

>
> Second, a complete transition to auto tools still feels like overkill at
> this point.
> But I agree that it could come one day.

With a lot of help (from people on this thread and for the same
reasons) I went through that agony with eclib.  I don't regret it but
I would not want to do it again!

John

> In any case, I am almost done with all the requested changes.
> I will follow up with a couple of quick questions, though.
>
>
> On Monday, October 10, 2016 at 5:09:48 PM UTC-4, Dima Pasechnik wrote:
>>
>>
>>
>> On Monday, October 10, 2016 at 9:09:38 PM UTC+1, François wrote:
>>>
>>> On 11/10/16 01:58, Victor Shoup wrote:
>>> > Another issue. I'm not sure if $(MAKE) is specific to gnu make or if it
>>> > is universal.
>>> > In general, I don't want to assume gnu. But I can certainly make this
>>> > the default,
>>> > and provide a config variable to override.
>>>
>>> I'll have another go at this when you use
>>> $(MAKE) inside a makefile you are making sure
>>> that the make command used is the same one that
>>> you called on the initial makefile.
>>>
>>> As other people mentioned it enable parallel make
>>> to proceed nicely, and in the case where there is
>>> several make command installed on the system
>>> you avoid funny things happening. I have AIX
>>> system which comes with its own posix make
>>> command. Something like ntl probably require
>>> gmake (GNU make), calling AIX make in the
>>> middle is not a good idea.
>>>
>>
>> Perhaps the most natural solution would be to change NTL build system so
>> that
>> it uses the standard autotools chain (autoconf/automake etc), not only
>> libtool.
>> Given that it uses very few external libraries, it ought to be an easy
>> task.
>>
>> Given that I am perhaps the only person in this thread who learned to
>> program using punch cards,
>> I am a dinosaur from an earlier period, yet, I look into the future :-)
>>
>> Dima
>>
>>
>>
>>> Francois
>
> --
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 09:38, Eric Gourgoulhon wrote:

Hi,

Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the message:

[openblas-0.2.19] ./openblas_utest: error while loading shared libraries: 
libgfortran.so.3: cannot open shared object file: No such file or directory


while fermat fails with the message:

[sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' 
already defined

See for instance https://patchbot.sagemath.org/ticket/18843/


It's annoying that only the patchbots have these errors, I have not seen 
anybody else report them.


--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Build issues with patchbots hades, poseidon and fermat

[Jeroen Demeyer]

On 2016-10-11 09:38, Eric Gourgoulhon wrote:

[sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' 
already defined


This looks like a typical error which was fixed by #21441. However, that 
ticket is merged, so I don't have an explanation.


If someone can give me access to this "fermat" machine, I could try to 
debug 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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Build issues with patchbots hades, poseidon and fermat

[Eric Gourgoulhon]

Hi,

Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the message:

[openblas-0.2.19] ./openblas_utest: error while loading shared libraries: 
libgfortran.so.3: cannot open shared object file: No such file or directory


while fermat fails with the message:

[sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' 
already defined
See for instance https://patchbot.sagemath.org/ticket/18843/

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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: a 7(!) year old (Singular) overflow issue still holds

[Jean-Pierre Flori]

Yes it is a feature of the Singular 4 update that Singular and Sage work by 
default with 16 bit exponents on 32 and 64 bit platform by default.
If only all of of you had read carefully the 543 comments of the update 
ticket and remembered this tcomment 
https://trac.sagemath.org/ticket/17254#comment:126 and commit 
https://git.sagemath.org/sage.git/commit/?id=8c0275427c66b709413188b82da7845a3196e4bb
 
that would be obvious to you.
Now if we want to give more bits when fewer variables are used that should 
be possible.
(I'm just kidding, this is a not so serious post except for the previous 
sentence.)

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: NTL v10

[Jean-Pierre Flori]

On Tuesday, October 11, 2016 at 6:06:50 AM UTC+2, Victor Shoup wrote:
>
> I looked at the singular patch, regarding the use of nothrow new.
> I dug up "ticket #852" which lead to that patch.
> In all honesty, it looks like singular is doing something wrong,
> so "fixing" NTL is just the wrong thing to do.
> So I won't implement that patch in NTL.
> This is a problem that should be fixed in singular, if it hasn't 
> been already.
>
> Yes this one is fishy, and as you can see I did not mention it here :)
Anyway we are currently transitioning to Singular 4 (woohoo) so there is 
hope this is not needed anymore.
In fact it was maybe already fixed before...

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.