I'm pretty sure some buildbot machine uses gcc5, though they might have a blacklisted gcc version where we build our own.
I would be perfectly happy to unconditionally supply -std=c++11 in src/setup.py, I just can't test that it fixes your issue. On Friday, October 21, 2016 at 2:51:17 PM UTC+2, Ralf Stephan wrote: > > Full make -j1 log attached. You'll see I correctly gave the first error. > I also think that the error message is clear in that a directive is > missing, instead of that the compiler did not understand C++11. So these > were remarkably shallow misdiagnoses, please try again. > > FWIW, gcc6 does not give this error, am I the only one trying to compile > with gcc5? Maybe the OpenSuSE gcc5 is configured differently (but still not > wrong)? > > On Fri, Oct 21, 2016 at 11:57 AM Jeroen Demeyer <jdem...@cage.ugent.be > <javascript:>> wrote: > >> On 2016-10-21 11:34, Francois Bissey wrote: >> > I’d like a serial log >> >> +1 >> >> General rule: when reporting build failures, try again without >> parallellism (make -j1) and report the log file of that. >> >> -- >> 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...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-r...@googlegroups.com >> <javascript:>. >> 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
