Updating flint version for GitHub testing of eclib

[John Cremona]

This is not a Sage issue but people here know how these things work better than I do:

My eclib repository on GitHub is set to test automatically when I push to the master branch. Recently the tests started to fail at the compilation stage, apparently because the version of FLINT in ubuntu-latest is not recent enough. Does anyone know how to get around that?

Before very long I will make a new release of eclib and it is likely that the Sage interface will need some adjustment. I am not looking forward to that as I now avoid building Sage unless I have to, so only build releases these days.

John

[John Cremona]

Thanks, Dima. That was very quick! I have merged your PR and will see what happens.

John

On Thu, 30 Apr 2026, 15:43 Dima Pasechnik, <dim...@gmail.com> wrote:

I've opened https://github.com/JohnCremona/eclib/issues/91 to deal
with your CI there

On Thu, Apr 30, 2026 at 9:38 AM Dima Pasechnik <dim...@gmail.com> wrote:

>
> On Thu, Apr 30, 2026 at 9:20 AM John Cremona <john.c...@gmail.com> wrote:
> >
> > This is not a Sage issue but people here know how these things work better than I do:
> >
> > My eclib repository on GitHub is set to test automatically when I push to the master branch. Recently the tests started to fail at the compilation stage, apparently because the version of FLINT in ubuntu-latest is not recent enough. Does anyone know how to get around that?
> >
>

> apply https://github.com/sagemath/sage/pull/42098
> ./bootstrap
>
> https://flintlib.org/doc/building.html
> get the latest flint 3.5, https://flintlib.org/download/flint-3.5.0.tar.gz
>  untar,
> ./configure
> make -j N
> sudo make install
> sudo ldconfig # just in case
> make check # just in case
>
> Flint 3.5 appears to be backward-compatible with 3.4, so as long as no
> new features from 3.5 are used
> 3.4 and 3.5 will all do.
>
> Now, your ./configure (in eclib, and in Sage) should be able to pick
> up flint 3.5
>
> HTH
> Dima

>
>
>
>
> > Before very long I will make a new release of eclib and it is likely that the Sage interface will need some adjustment. I am not looking forward to that as I now avoid building Sage unless I have to, so only build releases these days.
> >
> > John
> >

> > --
> > You received this message because you are subscribed to the Google Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> > To view this discussion visit https://groups.google.com/d/msgid/sage-devel/CAD0p0K4AszZAcv7A871F%2B-cS-23Q2X5dLY0mSPS-c1Zu8xnuVA%40mail.gmail.com.

[Dima Pasechnik]

On Thu, Apr 30, 2026 at 9:20 AM John Cremona <john.c...@gmail.com> wrote:
>

> This is not a Sage issue but people here know how these things work better than I do:
>
> My eclib repository on GitHub is set to test automatically when I push to the master branch. Recently the tests started to fail at the compilation stage, apparently because the version of FLINT in ubuntu-latest is not recent enough. Does anyone know how to get around that?
>

apply https://github.com/sagemath/sage/pull/42098
./bootstrap

https://flintlib.org/doc/building.html
get the latest flint 3.5, https://flintlib.org/download/flint-3.5.0.tar.gz
untar,
./configure
make -j N
sudo make install
sudo ldconfig # just in case
make check # just in case

Flint 3.5 appears to be backward-compatible with 3.4, so as long as no
new features from 3.5 are used
3.4 and 3.5 will all do.

Now, your ./configure (in eclib, and in Sage) should be able to pick
up flint 3.5

HTH
Dima

> Before very long I will make a new release of eclib and it is likely that the Sage interface will need some adjustment. I am not looking forward to that as I now avoid building Sage unless I have to, so only build releases these days.
>
> John
>

[Dima Pasechnik]

I've opened https://github.com/JohnCremona/eclib/issues/91 to deal
with your CI there

On Thu, Apr 30, 2026 at 9:38 AM Dima Pasechnik <dim...@gmail.com> wrote:
>

[John Cremona]

All fixed.  Thanks a lot, Dima!