I spend some time tonight on the gcc 4.4.0 porting problem and there
is only little work left to be done: I had resolved all issues in Sage
3.1.2, but neglected to merge all the fixed into subsequent releases.
Issues from 3.1.2 (3.4.2):
* gmp (gone in MPIR)
* ntl (Fixed in ntl-5.4.2.p7.spkg, need to add spkg-check before
posting spkg)
* fplll (update to 3.0.11 - or maybe a future 3.0.12 due to bug that
already existed in 2.x.)
* polybori - fixes:
* src/boost_1_34_1.cropped/boost/mpl/aux_/full_lambda.hpp +230
* src/boost_1_34_1.cropped/boost/mpl/apply.hpp +138
* src/boost_1_34_1.cropped/boost/mpl/bind.hpp +364
* src/boost_1_34_1.cropped/boost/mpl/bind.hpp +531
* src/boost_1_34_1.cropped/boost/mpl/apply_wrap.hpp +81
* src/boost_1_34_1.cropped/boost/mpl/apply_wrap.hpp +173
* clisp - *boom* - might be build problem - will use ecl in
4.0.alpha0 anyway
The main issue I ran into was a bug in libfplll that would crash the
doctest with some probability. The bug is also in the previous fplll
release and I have send a proposed fix upstream, so I am confident we
will have gcc 4.4 support in Sage 4.0. At least two people have either
complained in IRC, so the demand seems to clearly exist. :)
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
