[petsc-dev] related to compiling your source code

[Mark Adams]

>
> My point is - the fact they are carrying arround a .petscrc file [even
> if they don't know what it is] would qualify them as a petscrc
> user.
>
>

Certainly they are PETSc users and that is the problem.  This .petscrc file
gets sucked up without anyone knowing it.  It is a silent error and if it
is an old .petscrc file then it might have a % in it.  PETSc will try to
report that there is a problem but the error message gets garbled
sometimes.

We use "petsc.rc" because we do not see it as a system file and want to see
it with ls.  This causes confusion because no one would guess that petsc.rc
is treated by PETSc in the same as as .bashrc is treated by bash.

My point is that this is very error prone and impossible to figure out if
you know this bit of PETSc trivia.

Mark


> [otherwise how did this file get created at the original location
> [before getting into ~/? cosmic rays?]
>
> So  - I don't buy the argument " no one except satish uses petscrc"
>
> Satish
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150415/e393f91e/attachment.html>