Re: [sage-devel] NTL 9.7.0

2016-03-19 Thread François Bissey
On 03/15/16 09:28, François Bissey wrote: On 03/15/16 05:23, Victor Shoup wrote: That is a bummer with the C++11 issues. The way I see it, C++11 is the future, and pretty much all C++ must eventually deal with it. Looking over the build issues with singular -- if the make files don't respect CF

Re: [sage-devel] NTL 9.7.0

2016-03-19 Thread John Cremona
For eclib: in its configure.ac there is this: # Uncomment this to check for C++-11 compliance (no C++-11 features are used) #AX_CXX_COMPILE_STDCXX_11([],[optional]) so perhaps uncommenting that will make it work with the new NTL without any further tweaking? I don't have time to do this now but

Re: [sage-devel] NTL 9.7.0

2016-03-19 Thread Francois Bissey
> On 17/03/2016, at 21:59, John Cremona wrote: > > For eclib: in its configure.ac there is this: > > # Uncomment this to check for C++-11 compliance (no C++-11 features are used) > #AX_CXX_COMPILE_STDCXX_11([],[optional]) > > so perhaps uncommenting that will make it work with the new NTL > wi

Re: [sage-devel] NTL 9.7.0

2016-03-15 Thread Francesco Biscani
I remember that you mentioned some time ago that you were working on a solving (or working around) GMP's horrid error handling (especially with respect to memory errors). Did you make any progress on that front? Cheers, Francesco. On 12 March 2016 at 22:32, Victor Shoup wrote: > Just release

Re: [sage-devel] NTL 9.7.0

2016-03-14 Thread François Bissey
On 03/15/16 05:23, Victor Shoup wrote: That is a bummer with the C++11 issues. The way I see it, C++11 is the future, and pretty much all C++ must eventually deal with it. Looking over the build issues with singular -- if the make files don't respect CFLAGS or CXXFLAGS, then maybe one can make t

Re: [sage-devel] NTL 9.7.0

2016-03-14 Thread Victor Shoup
That is a bummer with the C++11 issues. The way I see it, C++11 is the future, and pretty much all C++ must eventually deal with it. Looking over the build issues with singular -- if the make files don't respect CFLAGS or CXXFLAGS, then maybe one can make the g++ command itself be a script that ca

Re: [sage-devel] NTL 9.7.0

2016-03-13 Thread Francois Bissey
By the way with thread disabled the update to ntl-9.7.0 in sage is almost trivial and doesn’t require any doctests change, I tested a few hours ago in sage-on-gentoo (I was already at 9.6.4 before that). François > On 13/03/2016, at 22:55, Volker Braun wrote: > > Surely we can compile singular

Re: [sage-devel] NTL 9.7.0

2016-03-13 Thread Francois Bissey
With threads enabled NTL includes c++11 headers that then get included in singular: https://bugs.gentoo.org/show_bug.cgi?id=572626 > On 13/03/2016, at 22:55, Volker Braun wrote: > > Surely we can compile singular with different cflags than NTL? Or is it a > linking problem? > > > On Sunday,

Re: [sage-devel] NTL 9.7.0

2016-03-13 Thread Volker Braun
Surely we can compile singular with different cflags than NTL? Or is it a linking problem? On Sunday, March 13, 2016 at 2:17:15 AM UTC+1, François wrote: > > Thanks for adding a way to make binaries without avx/fma. > > The threading unfortunately requires C++11 (unless it changed). > In turns

Re: [sage-devel] NTL 9.7.0

2016-03-12 Thread Francois Bissey
Thanks for adding a way to make binaries without avx/fma. The threading unfortunately requires C++11 (unless it changed). In turns the inclusion of c++11 flags breaks the building of the singular version shipped in sage. I don’t know about singular 4 but it wouldn’t surprise me if it did too. F

[sage-devel] NTL 9.7.0

2016-03-12 Thread Victor Shoup
Just released a new version of NTL! In a nutshell: faster, better matrix arithmetic over zz_p (small moduli), some improved thread pooling facilities, and several other small improvements. For more details, go here: http://shoup.net/ntl/doc/tour-changes.html -- You received this message because