On Fri, May 4, 2012 at 3:19 PM, Paulo César Pereira de Andrade
> /usr/include/givaro/givconfig.h:85:17: note: #pragma message:
> somebody nasty previously included <stdint.h> without
> __STDC_LIMIT_MACROS :)
This warning is all over the place, but so far, with the attached
linbox-integer.patch on top of an installed system it does not
fail earlier. But should get __STDC_LIMIT_MACROS defined
before the first c++ code includes stdint.h ...
Right, I had to do that with m4rie also.
> sage/libs/singular/singular.cpp:922:3: error: 'GFqDom'
does not name a type
> sage/libs/singular/singular.cpp: In function
Also an issue with m4rie. The problem is that there is now a
namespace involved, so you have to change all instances of GFqDom to
The attached sage-fedora-prepare.patch is another work in progress
patch, that should be helpful to give an idea of what needs to be patched
to build with newer linbox, sytem cudd, m4ri, m4rie, etc.
Okay, I'll look through it over the weekend. If you have parts that
you think are ready to go, the best thing to do is file a bug. That
way the patches won't get lost or forgotten.
Well, for singular, at least for now I think it is better to use
version used by sagemath, as polybori 0.7.1 (sagemath) to 0.8.1 (fedora)
appears to be going to require quite some work ...
Okay, we can pursue that path.
Incidentally, looking at the latest Singular release, I see that it
can use flint if it is available. We have flint 1.6, which I kept
deliberately because Sage's flint package is at 1.5.0. However,
Singular wants flint 2.3! What should we do there? Is there a part
of sage that really needs the older flint version, or should I upgrade
it for Singular?