[petsc-dev] CFLAGS and COPTFLAGS

[Satish Balay]

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.

./configure CC=gcc CXX=g++ FC=gfortran

Satish

> Same goes for package layout. There are about 100 packages in MacPorts
> that violate the standard layout of /include, /bin, /lib, etc. (this
> means having a folder named 'conf' is not allowed). That's less than
> 1%. Each of these packages causes extra work for the maintainer and
> makes us less likely to provide this package for other users.
>