On Dec 7, 4:07 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> 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.
Hhmmm, I am starting to see a potential pattern here. I will look into
the Solaris 9 failure later on today, and since it *lacks* a stdint.h
the *system* isn't C99 conform. I have been contemplating a while to
switch to Solaris 10 as primary development platform for the Solaris
port because it is much nicer in that regard. The main reason so far
is that I haven't build a proper toolchain on the Solaris 10/Sparc box
yet, but maybe it is time to do so. My Solaris 10U4/AMD 64 box has
some really, really odd linker bugs that I managed to work around, but
I might wait for 10U5 for Sun to fix them properly ;)
> 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.
I am not sure how much gmp 4.2.2 will fix this, but when I got Sage
2.8.15 to run with gcc 4.3 I had to do some fairly hackish things to
gmp.h. I would highly suggest revisiting the issue on 2.9.1 where I
plan to update Sage's gmp to 4.2.2 since finally all the licensing
issues will be taken care of.
> Carl Witty
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/
-~----------~----~----~----~------~----~------~--~---
