-
Notifications
You must be signed in to change notification settings - Fork 154
Checking FLINT version - #703
Conversation
jodavies
commented
Aug 25, 2025
For sensible runtimes we'd need to cache the flint build, as you do for the macos tests, for the linux jobs.
92f1868 to
39e2dd5
Compare
tueda
commented
Aug 26, 2025
Rebased onto #622.
39e2dd5 to
db91484
Compare
jodavies
commented
Sep 3, 2025
If we require at least v3.2.0, we could also remove the "workaround" here:
form/sources/flintinterface.cc
Lines 1724 to 1751 in e3eeea3
db91484 to
ed1328f
Compare
tueda
commented
Sep 4, 2025
If we require at least v3.2.0, we could also remove the "workaround" here:
Right. I have pushed a commit that completely removes the workaround.
Do you think we should leave an empty hook, like flint_startup_init in AllocSetups, just in case we need it again in the future?
jodavies
commented
Sep 4, 2025
I don't think so, it would be straightforward to add back in if it becomes necessary in the future.
jodavies
commented
Sep 5, 2025
At this point we should also recommend flint >=3.2.0 (and zstd) in the README.md and INSTALL files.
Disallow FLINT versions earlier than 3.2.0 by performing a preprocessor-based check during configure.
Add a runtime check that disallows FLINT versions earlier than 3.2.0. Note that the version check is also performed during the configure step. A runtime failure typically indicates that an incorrect shared library was linked.
We now require FLINT >= 3.2.0. The workaround is no longer necessary.
ce61f51 to
7813cf6
Compare
tueda
commented
Sep 30, 2025
TODO: README.md and INSTALL files must be updated.
Uh oh!
There was an error while loading. Please reload this page.
This PR adds checks both at configuration and at runtime to require FLINT 3.2.0 or later. Resolves #679.
(削除) Note: Many test jobs are currently failing due to old FLINT versions. (削除ここまで)Update: This PR depends on: