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. 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. Bill. On 7 Dec, 09:34, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Dec 7, 10:21 am, Bill Hart <[EMAIL PROTECTED]> wrote: > Bill, > > > Michael, if you want to fix the bug in the code you have in SAGE > > without getting the new tarball tonight, simply replace the 64 with > > FLINT_BITS on line 291 of fmpz_poly-test.c > > I will do that and see if the tests pass. > > > > > I've checked that this bug is not a problem elsewhere in that file. > > > Also you'll want to replace those handful of u_int64_t's with uint64_t > > else you will have problems in itanium or AIX or whatever it is. > > > Finally you'll want to grep for sys/types.h and replace with stdint.h > > throughout FLINT. It should occur three or four times. > > > Hlopefully fixing just these problems will make it compile out of the > > box on your SPARC32. > > But I will wait for the 1.01 tarball to update the official > FLINT.spkg, just to make sure that we ship vanilla releases in order > to avoid deviations that makes updates harder. > > > > > Bill > > <SNIP> > > Cheers, > > Michael --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
