Ralf Stephan wrote: > On Tuesday, April 28, 2015 at 6:03:26 PM UTC+2, leif wrote: > > Anyway, IMHO each package should check whether C++11 is supported. > > > That may not be sufficient because headers from eg pynac are included > in cythonized files and so errors are generated there. When adding the C++11 > switch to the compile flags other files whose headers require pre-C++11 > will barf. See the above ticket.
Which is what I meant by "(We'd still have to deal with that in some extension modules' extra_compile_args(?) for a while.)", and that doesn't exclude fixing some packages w.r.t. deprecated or non-standard features. Also, earlier versions of g++ do not *default* to C++11, so we'd (currently) have to add appropriate flags in module_list.py as well. -leif P.S.: While the GCC 4.6 and 4.7 series reached "end of life", there are still (LTS) releases using these. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
