On Dec 6, 12:43 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > Please touch devel/sage-main/sage/libs/flint/fmpz_poly.pyx and do a > "sage -b", otherwise the flint doctests will fail. The spkg runs the > FLINT test suite per default, so please report success as well as > failures here, together with info about CPU, operating system and > compiler.
I tried building FLINT 1.0 (as part of Sage 2.9.alpha1) on two computers. 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. On my 64-bit x86 Debian testing Linux box, running a prerelease of gcc 4.3, compilation failed, because gcc 4.3 in "-std=c99" mode switches to the standard meaning of inline, instead of the traditional gcc meaning. I've posted a complete bug report as #1415. Carl Witty --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
