On Tue, May 31, 2016 at 4:30 PM, François Bissey < [email protected]> 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 <https://groups.google.com/forum/#!searchin/sage-devel/polybori/sage-devel/9Uhnvm3wef8/kkGxWZ9QR0gJ> discussion or the ticket(s) attached to it, I expressly was not interested in being the maintainer (nor do I have any time now or in the foreseeable future to maintain it). However, despite that discussion no one stepped, and given that I think that it would be best to pursue the other path proposed in that discussion which was the removal of brial/polybori as a standard package (likely making it experimental given that it is unmaintained). > 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 integrate the few pull requests already there and whatever fix > it is for this. > > Francois > > > On 06/01/16 06:31, Dima Pasechnik wrote: > >> 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 SAGE_INSTALL_GCC set, as described in >> > >> >> http://doc.sagemath.org/html/en/installation/source.html#environment-variables >> < >> http://doc.sagemath.org/html/en/installation/source.html#environment-variables >> > >> >> >> <sigh> The shipped GCC doesn't seem to compile with GCC 6.1 </sigh> >> >> That might be related to -std defaulting to "gnu++14" and not >> "gnu++98"; >> I don't know. I tried figuring out how I could set the -std flag >> during >> build, but that build system is completely opaque for me. >> >> This is the last few lines spewed out by the failing compiler. Before >> that a gazillion C++11 warnings were printed: >> >> [install] [gcc-4.9.3.p1] In file included from ./tm.h:45:0, >> [install] [gcc-4.9.3.p1] from ../../src/gcc/cp/except.c:27: >> [install] [gcc-4.9.3.p1] ../../src/gcc/defaults.h:126:24: warning: >> invalid suffix on literal; C++11 requires a space between literal >> and string macro [-Wliteral-suffix] >> [install] [gcc-4.9.3.p1] fprintf ((FILE), >> ","HOST_WIDE_INT_PRINT_UNSIGNED",%un", ^ >> [install] [gcc-4.9.3.p1] In file included from >> ../../src/gcc/cp/except.c:1013:0: >> [install] [gcc-4.9.3.p1] cfns.gperf: In function 'const char* >> libc_name_p(const char*, unsigned int)': >> [install] [gcc-4.9.3.p1] cfns.gperf:101:1: error: 'const char* >> libc_name_p(const char*, unsigned int)' redeclared inline with >> 'gnu_inline' attribute >> [install] [gcc-4.9.3.p1] cfns.gperf:26:14: note: 'const char* >> libc_name_p(const char*, unsigned int)' previously declared here >> [install] [gcc-4.9.3.p1] cfns.gperf: At global scope: >> [install] [gcc-4.9.3.p1] cfns.gperf:26:14: warning: inline function >> 'const char* libc_name_p(const char*, unsigned int)' used but never >> defined >> [install] [gcc-4.9.3.p1] Makefile:1058: recipe for target >> 'cp/except.o' failed >> >> Best, >> Johan >> >> -- >> 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 [email protected] >> <mailto:[email protected]>. >> To post to this group, send email to [email protected] >> <mailto:[email protected]>. >> Visit this group at https://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. > -- Andrew -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
