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

leif wrote: > leif wrote: >> Benjamin Hackl wrote: >>> I have a very similar setup (gcc 6.1.1 20160602 on Arch Linux), and I'm >>> struggling quite hard to build 7.2: >>> >> [SNIP] >> >>> The next failure then occurs when the Sage library modules are compiled: >>> as I couldn't find out how to add

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

leif wrote: > Benjamin Hackl wrote: >> I have a very similar setup (gcc 6.1.1 20160602 on Arch Linux), and I'm >> struggling quite hard to build 7.2: >> > [SNIP] > >> The next failure then occurs when the Sage library modules are compiled: >> as I couldn't find out how to add '-std=gnu++98' for a

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

Benjamin Hackl wrote: > Hi, > > I have a very similar setup (gcc 6.1.1 20160602 on Arch Linux), and I'm > struggling quite hard to build 7.2: > > - I'm using the patch from https://trac.sagemath.org/ticket/20738 in > order to get singular to build. (Which works, as far as I can tell.) > - I could

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

Hi, I have a very similar setup (gcc 6.1.1 20160602 on Arch Linux), and I'm struggling quite hard to build 7.2: - I'm using the patch from https://trac.sagemath.org/ticket/20738 in order to get singular to build. (Which works, as far as I can tell.) - I could build (the originally failing) pack

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

Francois Bissey wrote: > 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. Oh, the Singular build errors with GCC 6.1 (C++14)

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

Francois Bissey wrote: > May you should post the associated config.log. Yep, emphasis on "the associated", as there's a chain of configure runs in different Singular folders. I'm not entirely sure, but presumably this 'configure' check for GMP already uses the generated local "copy" of gmp.h, so

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

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: > > Johan S. R. Nielsen wrote

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

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 th

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

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 the `CXXFLAGS= -std=gnu++98` as explaione

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

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

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

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] 7.3.beta2: Compilation failed with Brial

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] 7.3.beta2: Compilation failed with Brial

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

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

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: unordered_map: present but cannot be compiled configure: WARNING: unordered_map: chec

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

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: unordered_map: present but cannot be compiled configure: WARNING: unordered_map: check for missing prerequisite headers? config

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

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: unordered_map: present but cannot be compiled configure: WARNING: unordered_map: check for missing prerequisite headers? config

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

This seems to be the problem: checking unordered_map usability... no checking unordered_map presence... yes configure: WARNING: unordered_map: present but cannot be compiled configure: WARNING: unordered_map: check for missing prerequisite headers? configure: WARNING: unordered_map: see t

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

Most of that patch is not needed on linux but you should consider including the bit of it that was in a separate PR until today (when I noticed they had included it in the no-undefined.patch) https://github.com/BRiAl/BRiAl/pull/5 > On 1/06/2016, at 23:26, arojas wrote: > > The only difference i

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

El miércoles, 1 de junio de 2016, 12:58:10 (UTC+2), François escribió: > > Could you post your successful log, please? > > https://paste.kde.org/pz6cabvyk Note that this is the build log using Arch's PKGBUILD, not sage's spkg-install. The only difference is that we don't apply no-undefined.pat

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

Could you post your successful log, please? > On 1/06/2016, at 22:26, arojas wrote: > > > export CXXFLAGS+=' -std=gnu++98' before ./configure fixes this. Why passing > -std=gnu++98 to the compiler command (which brial already does) is not > enough, I have no idea. > > -- > You received thi

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

> Dima Pasechnik writes: > I presume it would be more productive to work on gcc 6.1 support in Sage, > rather than on building old gcc... Agreed. As is perhaps evident by now, I'm not knowledgeable enough about C++ to fix this myself. FWIW, this is now #20741. Best, Johan -- You received this

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

On Tue, May 31, 2016 at 6:03 PM, François Bissey < francois.bis...@canterbury.ac.nz> wrote: > On 06/01/16 12:45, R. Andrew Ohana wrote: > >> On Tue, May 31, 2016 at 4:30 PM, François Bissey >> > > wrote: >> >> Well Andrew Ohana is the maintainer of "bri

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

On 06/01/16 12:45, R. Andrew Ohana wrote: On Tue, May 31, 2016 at 4:30 PM, François Bissey mailto:francois.bis...@canterbury.ac.nz>> wrote: Well Andrew Ohana is the maintainer of "brial" but he doesn't have the time to take care of it apparently. I am not the maintainer, as per this

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

On Tue, May 31, 2016 at 4:30 PM, François Bissey < francois.bis...@canterbury.ac.nz> wrote: > Well Andrew Ohana is the maintainer of "brial" but he doesn't have the > time to take care of it apparently. I am not the maintainer, as per this

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

Well Andrew Ohana is the maintainer of "brial" but he doesn't have the time to take care of it apparently. We need someone else to get stuff in it. Mind you, I have no idea what the fix here would be. Someone with C++ knowledge needs to step in with a fix. Then another designed maintainer could i

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

I presume it would be more productive to work on gcc 6.1 support in Sage, rather than on building old gcc... Did you try reporting the brial problem upstream? https://github.com/BRiAl/BRiAl On Tuesday, May 31, 2016 at 3:43:23 PM UTC+1, Johan S. R. Nielsen wrote: > > > indeed, just build with SAG

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

> indeed, just build with SAGE_INSTALL_GCC set, as described in > http://doc.sagemath.org/html/en/installation/source.html#environment-variables The shipped GCC doesn't seem to compile with GCC 6.1 That might be related to -std defaulting to "gnu++14" and not "gnu++98"; I don't know. I tried f

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

> indeed, just build with SAGE_INSTALL_GCC set, as described in > http://doc.sagemath.org/html/en/installation/source.html#environment-variables Ah cool, thanks -- it seems now to be happily compiling away (though I can expect it to take a lot longer this time...) Of course, Brial still seems t

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

indeed, just build with SAGE_INSTALL_GCC set, as described in http://doc.sagemath.org/html/en/installation/source.html#environment-variables On Tuesday, May 31, 2016 at 1:17:04 PM UTC+1, John H Palmieri wrote: > > Can you force Sage to build its own GCC and use that instead? > > > On Tuesday, May

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

Can you force Sage to build its own GCC and use that instead? On Tuesday, May 31, 2016 at 1:33:25 PM UTC+2, Johan S. R. Nielsen wrote: > > > Downgrade GCC? > > Yummi -- a few hours well spent! > > Or just not contribute to Sage for a few weeks? > -- You received this message because you are

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

> Downgrade GCC? Yummi -- a few hours well spent! Or just not contribute to Sage for a few weeks? -- 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+

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

Downgrade GCC? -- 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...@googlegroups.com. To post to this group, send email to sage-release@googl

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

> Do I remember that g++ 6.1 is supposed to default to c++11? It looks like > that may be > the issue here. Anyone wants to either submit a fix for brial or work around > for the spkg? Looks to me in the logs like gcc gets the flag "-std=gnu++98"... Does anyone know at least a work-around for

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

Do I remember that g++ 6.1 is supposed to default to c++11? It looks like that may be the issue here. Anyone wants to either submit a fix for brial or work around for the spkg? François > On 30/05/2016, at 19:24, Johan S. R. Nielsen wrote: > > Hi, > > I'm having trouble compiling Sage 7.3.b

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

Hi, I'm having trouble compiling Sage 7.3.beta2 on Arch linux kernel 4.5.4-1, x86_64, 16GB ram. Looks like compiler-stuff. I have gcc 6.1.1 20160501. Snip of the compile error. Full brial build-log is attached: -- You received this message because you are subscribed to the Google Groups "sage