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'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. Bill On Dec 7, 9:15 am, Bill Hart <[EMAIL PROTECTED]> wrote: > Ouch, the problem is solved. In fact this test will fail on *all* 32 > bit machines. There is a really silly bug in the test code itself. The > function it tests is most likely fine. > > So this is definitely a bug. I will issue FLINT 1.01 this evening, > fixing this and the other problems we've noted. > > Thanks for the reports. > > So for Solaris you have two options. Either you'll need to make the > gcc c99 compliant if it is not already, or you can #define uint16_t, > uint32_t and uint64_t. I don't think I use any intN_t types anywhere, > so you shouldn't need to define those. > > Bill. > > On Dec 7, 9:08 am, Bill Hart <[EMAIL PROTECTED]> wrote: > > > On Dec 7, 3:07 am, Carl Witty <[EMAIL PROTECTED]> wrote: > > > > On my 32-bit x86 Debian testing Linux box, looking at install.log, one > > > test failed: > > > Testing _fmpz_poly_max_bits1()... FAIL! > > > (All other FLINT tests passed. The build is still running, so I don't > > > know whether Sage doctests will pass.) Let me know if you want more > > > information. > > > Hmm, this is an x86 machine. If it fails on this machine, I am now > > thinking I have a bug in the code rather than it being some kind of > > build problem. Perhaps this is what is happening on Michael's SPARC32. > > I better check my code. > > > The problem is more than likely going to be in the test code itself. > > I'll check it over with a fine tooth comb and see if I can find > > something wrong. > > > Bill. --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
