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 flint actually).
Francois
On 06/07/16 02:44, Florent Hivert wrote:
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
I would hope with g++6.1.
Which is of course not a long-term viable solution, but only a short-term
bugfix.
I just wan't to report that eclib have exactly the same problem.
Probably not, the issue in brial was that the fallback for compiling
without unordered_map was broken. I patched that already, so there isn't
anything left to see here.
Sorry I wasn't clear. What I reported is that the following packages
- brial
- eclib
- ppl
- singular
Doesn't compile on arch where the standard compiler is gcc-6.1 whose default
is to use c++11.
For those package, if the option -std=gnu++98 is not set. The compilation
fails. I didn't went all the way to check why.
Cheers,
Florent
--
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.
