OK, flint-1.0.1 is available now at http://www.flintlib.org/
With any luck this fixes all the issues we've found. The only changes are the bug fixes and some corrections and omissions for the manual. Bill. On 7 Dec, 16:29, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Dec 7, 10:41 am, Bill Hart <[EMAIL PROTECTED]> wrote: > > > Sounds sensible. I'll get to work on making that new tarball as soon > > as I get back from Real Job TM. > > :) > > > In the meantime it would be great to hear if changing the u_int64_t's > > to uint64_t's and changing the #includes actually fixes it so it > > compiles out of the box on SPARC32. > > That doesn't work. The compiler doesn't use its own stdint.h instead. > I have never figured out why. This doesn't matter to me any longer > since after some IRC discussion with William we decided to move to > Solaris 10 as primary dev platform for Sage on Solaris which does have > a stdint.h :) > > > I think it probably should, since you seem to pick up a uint16_t from > > somewhere without defining it, so my thinking is that it probably is > > c99 compliant after all. > > Ahhh, in an ideal world those bugs would get fixed, but in reality we > need to work around them. I spend a lot of my time on Sage fixing > issues that aren't supposed to be there :) > > > Bill. > > With the FINT_BITS macro instead of "64" the test suite passes on that > Sparc box. > > Cheers, > > Michael > > <SNIP> --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
