#12173: Update FLINT to 2.3
---------------------------------------------------------------------+------
Reporter: mhansen |
Owner: tbd
Type: enhancement |
Status: needs_review
Priority: major |
Milestone: sage-5.9
Component: packages |
Resolution:
Keywords: flint spkg | Work
issues:
Report Upstream: N/A |
Reviewers: John Cremona
Authors: Mike Hansen, Fredrik Johansson, Jean-Pierre Flori |
Merged in:
Dependencies: #12433 |
Stopgaps:
---------------------------------------------------------------------+------
Comment (by jpflori):
Replying to [comment:231 leif]:
> Replying to [comment:227 jpflori]:
> > Replying to [comment:225 leif]:
> > > Replying to [comment:224 jpflori]:
> > > > Do you suggest we keep the "#define ulong unsigned long"?
> > > > I don't really care.
>
> `for f in $SOURCES; do sed -i 's/ulong/mp_limb_t/g' $f; done` ;-)
>
> [[BR]]
>
> > > I think we should [better?] coordinate that with upstream (probably
including changes to the weird `configure` and `Makefile.in`, too --
haven't looked at FLINT's current state recently at all).
> > You can just propose whatever changes you want to include here, I'm in
close contact with upstream, especially for the build system, so I'll take
care of coordination.
> > I agree there is some fishy things going on with FLINT_TUNE and CFLAGS
and surely other things.
> >
> > And don't say "let's switch to autotools" unless you wanna be in
charge of the build system maintenance as Bill Hart will definitely not
want to maintain it.
>
> :-) Yes. I just meant I don't know if there are any changes in
progress w.r.t. this.
Not that I am aware of, so unless Bill posts here and rants we all should
assume so.
>
> It doesn't seem we'd need any ''Sage-specific'' changes, so IMHO we
should take fixes from upstream, or push (generic) changes there.
>
>
> > Be also aware there won't be any FLINT release before at least the dev
meeting in may.
>
> Yes. But FLINT 2.3.1 should (already) include any fixes we (and others)
need, see above.
Of course, its just I'm getting tired by this ticket and don't want to
wait for the 2.3.1 release which at best will happen in mid-may and then
all the stuff here will have to be rebased again...
And that's optimistic because I guess most people at the FLINT meeting
will expect to work with FLINT 2.3 and this spkg and will implement new
features in FLINT/Sage, rather than working on the FLINT build system and
trying to push a new release.
So I feel our best shot is to get
http://boxen.math.washington.edu/home/jpflori/flint-2.3.p0.spkg.14241 in
as it just modifies flint-2.3 minimally to make it work on OS X.
Let's keep the C99, strange env variables fun for a later FLINT
release/Sage spkg if its not definitely needed to let Sage work on
supported systems.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12173#comment:232>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
