[petsc-users] Petsc configuration and multiple branch working

Barry Smith bsmith at mcs.anl.gov
Sat Sep 6 19:59:52 CDT 2014


  What will I do with all this new freed up time? Does it work in Xcode?

  Barry

On Sep 6, 2014, at 7:09 PM, Matthew Knepley <knepley at gmail.com> wrote:

> On Sat, Sep 6, 2014 at 6:03 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> 
>    How do you use ccache?  Do you do this “weird” thing
> 
> To install for the second method, do something like this:
> 
> --with-cc='ccache gcc' --download-mpich
> 
> works fine.
> 
>    Matt
>  
> cp ccache /usr/local/bin/
> ln -s ccache /usr/local/bin/gcc
> ln -s ccache /usr/local/bin/g++
> ln -s ccache /usr/local/bin/cc
> ln -s ccache /usr/local/bin/c++
> 
>    Thanks
> 
>    Barry
> 
> 
> 
> On Sep 6, 2014, at 5:50 PM, Jed Brown <jed at jedbrown.org> 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.
> 
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener



More information about the petsc-users mailing list