Skip to content

Conversation

@stephankramer
Copy link
Contributor

@stephankramer stephankramer commented Oct 22, 2025

This combines a few updates now:

  • (most of) https://github.com/dsroberts/fluidity/tree/dsroberts/noble including fixes for petsc v3.19 and support for configuring with vtk 9 from autoconf. Except the manual changes (which break on Jammy). Keeping the gmsh version at 2.6 in the Docker container for now (to be fixed later).
  • drop Bionic and Focal builds
  • fixes for petsc 3.23/3.24. One open issue is that with a debug petsc build it spews a lot of warnings, which I attempted to fix but that seemed to change answers for reasons I don't understand. See bbe7ea0 for the reversal of that "attempted fix". Again I will leave that for now as without the fix, everything seems to work.

dsroberts and others added 8 commits July 15, 2025 14:54
It appears using the rules Makefile - which provide getlinklibs and
getincludedirs targets - is not consistent between different versions.
Now mimicking these by printing combinations of export variables from
"variables" Makefile

Dropping older version of petsc makefile.
@stephankramer stephankramer force-pushed the fix-petsc-makefile branch 8 times, most recently from c3c1dae to ff404b4 Compare October 29, 2025 13:53
stephankramer and others added 6 commits October 29, 2025 14:31
It seems to change answers, although I don't understand why.
This is the oldest petsc version I care about (Jammy)
Let's tackle this in a separate PR as I think switching
breaks a number of tests - most of these we might care
about but we should probably look a bit closer before
merging.
@stephankramer stephankramer changed the title Use petsc variables Makefile only. Updates for VTK9 and PETSC 3.15-24 Oct 29, 2025
Includes Build, short, medium and unit tests
Copy link
Contributor

@Patol75 Patol75 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! Changes look good, and they come with successful CI runs. You probably need to modify the expected CI checks in the repository settings, but apart from that, the work is pretty much done.

Changes in 4fb595c
are needed but break Jammy. TODO: switch over to build
manual on Noble, not Jammy
With gfortran 13 (noble) despite the cleverness our is_nan check is
beaten by the compiler optimisation.
@stephankramer stephankramer merged commit e28a4ab into main Oct 30, 2025
0 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants