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

2016-10-12 Thread Dima Pasechnik 
I see, thanks. I should have been cc'ng myself on #21567 long ago.

Anyway, is it the time we open a meta-ticket on enabling full build of Sage 
with clang(++) ?
(and creating a gfortran package to deal with fortran)

It seems to be within reach nowadays.

On Tuesday, October 11, 2016 at 9:35:20 PM UTC, John H Palmieri wrote:
>
>
>
> 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

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

2016-10-11 Thread 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

2016-10-11 Thread 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] Re: trouble compiling latest sage development version

2016-10-11 Thread 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] Re: trouble compiling latest sage development version

2016-10-11 Thread 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] Re: trouble compiling latest sage development version

2016-10-11 Thread 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

2016-10-11 Thread 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 "/Applica

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

2016-10-11 Thread 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 in

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

2016-10-11 Thread 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'.
>>> [ma

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

2016-10-11 Thread 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 1:16:02

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

2016-10-11 Thread 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 sage-devel+...@googlegroups.com. 
 > To post t

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

2016-10-11 Thread 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.

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

2016-10-01 Thread Dima Pasechnik 


On Saturday, October 1, 2016 at 8:16:02 AM UTC, Volker Braun wrote:
>
> My suggestion would be to upgrade to xcode 10.11, 
>
to OSX 10.11, that is...
 

> 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.

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

2016-10-01 Thread Volker Braun 
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.

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

2016-09-30 Thread Anne Schilling 
I am not sure. I just compiled sage-7.3 released 2016-8-04 and it went 
fine, so I think it must be related
to some new patches in the new development branch ...

Anne

On Friday, September 30, 2016 at 7:08:35 PM UTC-7, François wrote:
>
> Does the ntl failure look like anything reported at 
> 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.

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

2016-09-30 Thread Francois Bissey 
Does the ntl failure look like anything reported at 
https://trac.sagemath.org/ticket/20779 ?

François

> On 1/10/2016, at 14:52, Travis Scrimshaw  wrote:
> 
> Perhaps this is from the same error as stack overflow post? I remember we had 
> to have something with '-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+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.