Re: [sage-release] 7.3.beta2: Compilation failed with Brial

2016-06-06 Thread Florent Hivert
On Tue, Jun 07, 2016 at 01:51:05PM +1200, François Bissey wrote: > While some of that stuff is not completely surprising, some is. > I have compiled a number of those with gcc-5.3 and -std=c++11 > for various reasons. Could you provide log for eclib, ppl (ok > that one is new) and singular. Also po

Re: [sage-release] 7.3.beta2: Compilation failed with Brial

2016-06-06 Thread François Bissey
While some of that stuff is not completely surprising, some is. I have compiled a number of those with gcc-5.3 and -std=c++11 for various reasons. Could you provide log for eclib, ppl (ok that one is new) and singular. Also possibly ntl as things happening there will affect eclib and singular (and

Re: [sage-release] 7.3.beta2: Compilation failed with Brial

2016-06-06 Thread Florent Hivert
Dear Vorlker, On Mon, Jun 06, 2016 at 06:18:12AM -0700, Volker Braun wrote: > On Monday, June 6, 2016 at 5:10:36 AM UTC-4, hivert wrote: > > > > > C++11 appears to be a bit much for brial, but moving the -std=gnu++98 > > > into configure before any tests are run does appear to work here and

Re: [sage-release] Sage 7.3.beta3 released

2016-06-06 Thread Jeroen Demeyer
On 2016-06-05 19:16, Volker Braun wrote: 8c68331 Trac #20721: Unpack all upstream tarballs into 'src' directory Is it possible that this made uncompressing a lot slower? On one machine, the GCC tarball is taking already 16 minutes CPU time to uncompress... -- You received this message becau

Re: [sage-release] 7.3.beta2: Compilation failed with Brial

2016-06-06 Thread Volker Braun
On Monday, June 6, 2016 at 5:10:36 AM UTC-4, hivert wrote: > > > C++11 appears to be a bit much for brial, but moving the -std=gnu++98 > > into configure before any tests are run does appear to work here and > > I would hope with g++6.1. > Which is of course not a long-term viable solution, but

Re: [sage-release] Sage 7.3.beta3 released

2016-06-06 Thread Jeroen Demeyer
This worries me: missing cimport in module '.': ./sage/rings/rational.pxd missing cimport in module '.': sage/rings/rational.pxd It might mean that some dependencies are not correctly picked up by Cython. -- You received this message because you are subscribed to the Google Groups "sage-releas

[sage-release] Re: Sage 7.3.beta3 released

2016-06-06 Thread Eric Gourgoulhon
Build OK + make ptestlong passed on Ubuntu 15.10 x86_64 Xeon E5-2623 + 16 GB RAM. Eric. -- 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..

Re: [sage-release] 7.3.beta2: Compilation failed with Brial

2016-06-06 Thread Florent Hivert
On Thu, Jun 02, 2016 at 03:12:59PM +1200, François Bissey wrote: > On 06/02/16 09:29, François Bissey wrote: > >On 06/02/16 03:23, arojas wrote: > >>This seems to be the problem: > >> checking unordered_map usability... no > >> checking unordered_map presence... yes > >> configure: WARNING: unorder