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

2016-06-18 Thread kcrisman
On Saturday, June 18, 2016 at 9:56:14 AM UTC-4, Volker Braun wrote: > > This is http://trac.sagemath.org/ticket/20842 > > It seems that the script is accidentally quadratic in the number of > filenames, and gcc has almost 100k files... > >> >> Thanks; I just destroyed my only working Sage on

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

2016-06-18 Thread Francois Bissey
May you should post the associated config.log. For singular it is usually not enough to define CPPFLAGS. I would have gone with CXX=“g++ -std=gnu++98” there are places in singular where CPPFLAGS/CFLAGS are not used. François > On 19/06/2016, at 00:37, leif wrote: > >

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

2016-06-18 Thread Volker Braun
This is http://trac.sagemath.org/ticket/20842 It seems that the script is accidentally quadratic in the number of filenames, and gcc has almost 100k files... On Saturday, June 18, 2016 at 2:56:41 PM UTC+2, kcrisman wrote: > > > > On Saturday, June 18, 2016 at 7:01:47 AM UTC-4, leif wrote: >>

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

2016-06-18 Thread Jan Groenewald
Hi On 18 June 2016 at 02:53, kcrisman wrote: > Had to make distclean && make but it had an awful long time setting up > build directory for gcc (prior stuff did fine) and then after interrupting > (after like a half hour), the entire gcc pkg log is: > > Found local metadata

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

2016-06-18 Thread kcrisman
On Saturday, June 18, 2016 at 7:01:47 AM UTC-4, leif wrote: > > Volker Braun wrote: > > KeyboardInterrupt means you pressed Ctrl-C (or maybe your cat ran over > > the keyboard) > > But it took the cat about half an hour to get bored by "Setting up build > directory for gcc-4.9.3.p1" (or

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

2016-06-18 Thread leif
Johan S. R. Nielsen wrote: > I just want to follow up on my compilation misadventures: I'm still not > able to compile Sage with gcc-6.1 on Arch. After two weeks of not being > able to review tickets, I have now rolled back my gcc and can get back > to work. > > I managed to compile Brial using

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

2016-06-18 Thread leif
Volker Braun wrote: > KeyboardInterrupt means you pressed Ctrl-C (or maybe your cat ran over > the keyboard) But it took the cat about half an hour to get bored by "Setting up build directory for gcc-4.9.3.p1" (or probably less, and then a couple of minutes to figure out how to press Ctrl-C, I