[petsc-users] Petsc configuration and multiple branch working

[Satish Balay]

On Sat, 6 Sep 2014, Jed Brown wrote:

> Barry Smith <bsmith at mcs.anl.gov> writes:
> 
> >    The problem with using different PETSC_ARCH for each branch is that
> >    when you switch the branches it will sometimes/often change an
> >    include file that many of the C files are dependent on so make
> >    gmake will require recompiling much of the library, with different
> >    working directories this will not happen.
> 
> I use ccache so that those "recompiles" take less than 10 seconds on
> average.  I don't think having a separate clone per branch is useful, so
> I just have one clone and about 50 PETSC_ARCHes within it.  Reconfigure
> is usually not necessary unless you have to go way back in history.


fedora linux defaults to using ccache - I guess I've been using it all along..
Do you do any additional tuning of ccache?

$ type gcc g++
gcc is /usr/lib64/ccache/gcc
g++ is /usr/lib64/ccache/g++

Satish