I have added two MR to hopefully improve PETSc usability based on your issues
https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7663__;!!G_uCfscf7eWS!efrDwkgUkc276It23vyi4kUxZ3ieab1AgseqAOCvE-K9-nLNjd6aad4rmdaRExARms_zfeExsNtm5lRx_b5ezSM$  Add information to template Makefile.user indicating what parts can easily be... (!7663) · Merge requests · PETSc / petsc · GitLab gitlab.com to clarify in Makefile.User how to remove the PETSc build compiler flags and https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/merge_requests/7662__;!!G_uCfscf7eWS!efrDwkgUkc276It23vyi4kUxZ3ieab1AgseqAOCvE-K9-nLNjd6aad4rmdaRExARms_zfeExsNtm5lRxbVNm9-g$  Additional documentation in configure for CFLAGS and friends (!7662) · Merge requests · PETSc / petsc · GitLab gitlab.com additional clarification in the docs for CFLAGS and friends and how they work Barry > On Jul 1, 2024, at 12:08 PM, meator <[email protected]> wrote: > > On 7/1/24 5:23 PM, Stefano Zampini wrote: >> This is unfortunate. I assume that patching the buildsystem or some >> other trickery will be necessary if what you're saying is true. >> I admit it is not so standard, but Satish always opposed this. >> No need to hack the buildsystem, just use COPTFLAGS, CXXOPTFLAGS and >> FOPTFLAGS > > I will try using *OPTFLAGS, thanks! > >> I don't think you should use Makefile.user. That is there as a sort of >> template/placeholder. The extra variables are not included in a standard >> usage of pkgconfig, so I don't think this issue is "severe" > > This is not a choice I get to make. The users of my package may choose to use > PETSc however they want. And /usr/share/petsc/Makefile.user or > /usr/share/petsc/CMakeLists.txt are officially supported ways of using PETSc, > so deciding to ignore these use cases and leaving junk flags in > /usr/lib/pkgconfig/petsc.pc is not tolerable for me. > <OpenPGP_0x1A14CB3464CBE5BF.asc>
