[petsc-dev] CFLAGS and COPTFLAGS

[Sean Farley]

balay at mcs.anl.gov writes:

> On Sun, 19 Jan 2014, Sean Farley wrote:
>
>> I haven't chimed in for this thread but I'd like to point out that this
>> CFLAGS trickery is also a problem for package maintainers. These people
>> are usually admins and have no specific knowledge of PETSc
>> internals. Every single time a package does something outside the norm
>> for configure makes us curse. A lot.
>> 
>> For example, PETSc is the only project in all of 17963 ports of MacPorts
>> that doesn't accept CC, CXX, FC, etc. for changing its compiler for
>> configure. These types of variables are set outside of the port file
>> (i.e. in the base system of MacPorts) and make it annoying to deal with
>> PETSc.
>
> To clarify - petsc configure ignores CC etc from env - but the following is accepted.

The environment is already set in base since every other package accepts
it. You can, of course, do whatever you want. Just don't expect package
maintainers to want to spend this kind of effort.