You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Taking the libMesh ANY_WERROR_FLAG value ought to be safe, if you want us to add something on the libMesh side to export it.
Taking libMesh ANY_PARANOID_FLAGS would be safe by itself, but not in combination with -Werror, because I expect the sequence of "Roy notices a new compiler warning option, fixes all the libMesh warnings it triggers, then adds it to the list of libMesh paranoid warnings" will happen over and over again, and if GRINS just scarfs the libMesh list then any --enable-werror --enable-paranoid-warnings builds will suddenly fail after a corresponding libMesh upgrade.
libMesh/libmesh#1797, libMesh/libmesh#1800, libMesh/libmesh#1812
We don't want to just take those by default when grabbing libMesh flags, I think, better to just configure separately on the GRINS side.
The text was updated successfully, but these errors were encountered: