[sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Volker Braun
As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html e6cae6d88d (tag: 8.2.beta5, trac/develop) Updated SageMath version to 8.2.beta5 9dd4282d36 Trac #24660: Memory leak i

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
Note that from this release a fresh build on OS X will use clang. Building gcc and using it can be triggered with SAGE_INSTALL_GCC=yes as usual. Incremental upgrade will continue to use the previously configured compiler. Feedback on optional packages that are broken by the move appreciated. Franç

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan
So how to use clang on Linux? On Fri, Feb 9, 2018 at 9:36 AM François Bissey wrote: > Note that from this release a fresh build on OS X will use clang. > Building gcc and using it can be triggered with SAGE_INSTALL_GCC=yes > as usual. > Incremental upgrade will continue to use the previously con

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
> On 9/02/2018, at 23:03, Ralf Stephan wrote: > > So how to use clang on Linux? CC=clang CXX=clang++ make Adjust to the peculiarity of your install in terms of PATH and compiler names. François -- You received this message because you are subscribed to the Google Groups "sage-release" gro

[sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
An incremental build from previous beta fails on gfortran : [gfortran-7.2.0] Found local metadata for gfortran-7.2.0 [gfortran-7.2.0] Using cached file /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz [gfortran-7.2.0] gfortran-7.2.0 [gfortran-7.2.0] ==

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
Which version of ubuntu? We have seen an instance of that problem during review but we thought it was fixed. OK, there was something nagging me but it looked fixed on the patchbot. > On 9/02/2018, at 23:56, fchapot...@gmail.com wrote: > > An incremental build from previous beta fails on gfortran

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
ubuntu 17.10. There is also at least one patchbot having the same issue, see https://patchbot.sagemath.org/ticket/0/ Le vendredi 9 février 2018 12:02:28 UTC+1, François Bissey a écrit : > > Which version of ubuntu? We have seen an instance of that problem during > review > but we thought it was

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
Actually if you have the autotools packages installed (from the system or sage) can you try autoreconf -i then re-run configure and see if that fix it. > On 10/02/2018, at 00:02, François Bissey wrote: > > Which version of ubuntu? We have seen an instance of that problem during > review > but

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
I did a make distclean and make. Everything built smoothly. Le vendredi 9 février 2018 12:10:40 UTC+1, François Bissey a écrit : > > Actually if you have the autotools packages installed (from the system or > sage) > can you try > autoreconf -i > then re-run configure and see if that fix it.

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread Jeroen Demeyer
On 2018-02-09 11:56, fchapot...@gmail.com wrote: An incremental build from previous beta fails on gfortran : Please do touch configure.ac && make build and send me the full output. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscr

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
I sent something at your lri adress. Le vendredi 9 février 2018 13:52:24 UTC+1, Jeroen Demeyer a écrit : > > On 2018-02-09 11:56, fchap...@gmail.com wrote: > > An incremental build from previous beta fails on gfortran : > > Please do > > touch configure.ac && make build > > and send me the fu

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread Jeroen Demeyer
I think I understand why this might happen: https://trac.sagemath.org/ticket/24694 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googl

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread Jeroen Demeyer
On 2018-02-09 12:02, François Bissey wrote: We have seen an instance of that problem during review but we thought it was fixed. That was a different issue. While the error message was the same, the underlying reason was different. -- You received this message because you are subscribed to th

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan
Trying clang on Linux, after make distclean fails in giac but I'm not sure if my installation is the reason. TLDR: ./index.h:571:11: error: no template named 'hash_map' in namespace 'std'; did you mean '__gnu_cxx::hash_map'? giac compile log is attached -- You received this message because you a

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan
This is now https://trac.sagemath.org/ticket/24696 On Fri, Feb 9, 2018 at 3:35 PM Ralf Stephan wrote: > Trying clang on Linux, after make distclean fails in giac but I'm not sure > if my installation is the reason. TLDR: > ./index.h:571:11: error: no template named 'hash_map' in namespace 'std';

[sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
I have a build failure in subprocess32 on a python3 build (using export SAGE_PYTHON3=yes) [subprocess32-3.2.7] Found local metadata for subprocess32-3.2.7 [subprocess32-3.2.7] Attempting to download package subprocess32-3.2.7.tar.gz from mirrors [subprocess32-3.2.7] http://www.mirrorservice.or

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
OK, that’s a slightly different issue. I didn’t think that would be a problem but this package shouldn’t be needed with python3.2+ since it is a backport of functionality for older python. So it would be best not to install it with python3. > On 10/02/2018, at 05:55, fchapot...@gmail.com wrote:

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread Jeroen Demeyer
On 2018-02-09 17:55, fchapot...@gmail.com wrote: I have a build failure in subprocess32 on a python3 build (using export SAGE_PYTHON3=yes) Fixed in https://trac.sagemath.org/ticket/24650 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsu

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
Volker, it would be great (and I would appreciate) if you could set up a buildbot that checks that sage builds with python3. One can not yet say that vanilla-sage builds and starts with "export SAGE_PYTHON3=yes", but at least it builds (since some time already). Starting is another matter, but

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread Volker Braun
Can you first set up a makefile target that is supposed to be tested? E.g. "make test-python3" builds with py3 and eventually gets extended to test things that already work? On Friday, February 9, 2018 at 9:15:04 PM UTC+1, fchap...@gmail.com wrote: > > Volker, it would be great (and I would ap

Re: [sage-release] Re: Sage 8.2.beta5 released

2018-02-09 Thread fchapoton2
This is way above my understanding of "make" matters. So help from Erik or Jeroen or whoever is knowledgeable in this kind of things, is required. Le vendredi 9 février 2018 21:24:34 UTC+1, Volker Braun a écrit : > > Can you first set up a makefile target that is supposed to be tested? E.g. >

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Justin C. Walker
> On Feb 9, 2018, at 00:25 , Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git branch. > Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html Yay for using clang! Built from a fresh clone/checkout of

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
We didn’t test clang 3.7 which is what your machine is using at OS X 10.11. But I recognised the error as one I got in the same place when I tried a build with icc on linux. Yes that’s a fun bit I haven’t mentioned yet. You can technically try any compiler that pretends to be gcc - but only clang

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread kcrisman
On Friday, February 9, 2018 at 10:32:49 PM UTC-5, François Bissey wrote: > > We didn’t test clang 3.7 which is what your machine is using at OS X > 10.11. Would that be the same as this one? I also have 10.11. $ clang --version Apple LLVM version 7.3.0 (clang-703.0.31) Target: x86_64-appl

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
> On 10/02/2018, at 18:06, kcrisman wrote: > > On Friday, February 9, 2018 at 10:32:49 PM UTC-5, François Bissey wrote: > We didn’t test clang 3.7 which is what your machine is using at OS X 10.11. > > Would that be the same as this one? I also have 10.11. > > $ clang --version > > Apple LL

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Justin C. Walker
> On Feb 9, 2018, at 19:32 , François Bissey wrote: > > We didn’t test clang 3.7 which is what your machine is using at OS X 10.11. > But I recognised the error as one I got in the same place when I tried a build > with icc on linux. Yes that’s a fun bit I haven’t mentioned yet. > You can techni

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread François Bissey
> On 10/02/2018, at 19:40, Justin C. Walker wrote: > > Thanks for this. I have > > Apple LLVM version 7.0.2 (clang-700.1.81) > Target: x86_64-apple-darwin15.6.0 > Thread model: posix > > Is there a fairly straight-forward way to get Apple’s clang at what you're > calling 3.8? Can you ins

Re: [sage-release] Sage 8.2.beta5 released

2018-02-09 Thread Ralf Stephan
After building with clang on OpenSuSE two dozen doctests fail, all due to segfault in linbox: File "sage/matrix/matrix_modn_sparse.pyx", line 730, in sage.matrix.matrix_modn_sparse.Matrix_modn_sparse._rank_linbox (build/cythonized/sage/matrix/matrix_modn_sparse.c:9008) sig_on() S