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

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,

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

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

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

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

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

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,

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

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

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): >

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

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

2016-10-01 Thread leif
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

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

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

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

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

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

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

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

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

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

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

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

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