[petsc-dev] related to compiling your source code

Satish Balay balay at mcs.anl.gov
Tue Apr 14 16:05:38 CDT 2015

On Tue, 14 Apr 2015, Mark Adams wrote:

> > using "-pc_type_hypre" in ~/.petscrc is a bad practice. [it makes
> > sense only for global options that are useful for multiple petsc
> > applications - like -malloc_dump]
> >
> >
> The problem is that users pass rc files around, scp, mail, whatever, and
> they put it their home directory temporarily and leave it there.
> It is just very error prone and the error is really hard to figure out.
> Many computational scientists would not cut is Linux developers but PETSc
> has to deal with them (eg, me!).  My users just don't want to know much
> about PETSc, which makes it worse -- the users don't know much about PETSc
> but they have to deal with the rc interface.

How about when they copy their .bashrc file - which might include
PETSC_OPTIONS env variable?  [or LD_LIBRARY_PATH to wrong version of

Is the current thought to remove PETSC_OPTIONS env variable aswell?

How about PWD/.petscrc and PWD/petscrc? remove them aswell?


More information about the petsc-dev mailing list