Re: [petsc-dev] Fortran equivalent + separate output with output_file

2020-01-17 Thread Pierre Jolivet
It’s weird that the tests are running OK on linux-pkgs-opt, but not on my naked Linux VM. If that’s not too much to ask, could you please fetch jolivet/feature-hpddm-cleanup, ./configure --download-slepc --download-hpddm And then, make -f gmakefile test globsearch='ksp_ksp_tutorials-ex76f_*'

Re: [petsc-dev] Fortran equivalent + separate output with output_file

2020-01-17 Thread Smith, Barry F. via petsc-dev
Better to send more details. What function are you calling, what is the full error stack. Much quicker for us to help you then repeated email (you can never send too much information about a crash). PETSC_NULL_FUNCTION is the thing to use, but it is completely manual to for us to put

Re: [petsc-dev] Fortran equivalent + separate output with output_file

2020-01-17 Thread Pierre Jolivet
> On 13 Jan 2020, at 4:38 PM, Smith, Barry F. wrote: > > > >> On Jan 13, 2020, at 9:32 AM, Pierre Jolivet >> wrote: >> >> Hello, >> This is actually two separate questions, sorry. >> 1) I’m looking for the Fortran equivalent of the following, but I couldn’t >> get any help looking at the

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Jed Brown
"Balay, Satish" writes: > I guess you can just create links [from mpicc to ccache] instead of > these wrapper scripts in these locations - with the same ccache > performance? I don't because I have multiple mpicc at different paths. > And with the scripts [mpicc/mpicxx links to ccache] in PATH

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Balay, Satish via petsc-dev
I guess you can just create links [from mpicc to ccache] instead of these wrapper scripts in these locations - with the same ccache performance? And with the scripts [mpicc/mpicxx links to ccache] in PATH - you don't need --with-mpi-dir [and mpiexec/include/lib work-around] Also is there an

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Scott Kruger
I didn't realize brew put the links in libexec. I did it manually like in this tutorial: https://software.intel.com/en-us/articles/accelerating-compilation-part-1-ccache This tutorial discusses the size of the cache. I made mine too small when I first set it up. I like Jed's mpi

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Jed Brown
"Balay, Satish via petsc-dev" writes: > I have ccache setup automatically on my linux box. > > balay@sb /home/balay > $ which gcc > /usr/lib64/ccache/gcc > > i.e the easiest thing to do is update PATH. For ex on OSX [where its > not automatically setup] - I have it installed via brew and:

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Balay, Satish via petsc-dev
I have ccache setup automatically on my linux box. balay@sb /home/balay $ which gcc /usr/lib64/ccache/gcc i.e the easiest thing to do is update PATH. For ex on OSX [where its not automatically setup] - I have it installed via brew and: export PATH=/usr/local/opt/ccache/libexec:$PATH Satish

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Jed Brown
To use system MPI, I made a directory with one-line scripts $ rg . ~/usr/ccache/mpich/ /home/jed/usr/ccache/mpich/bin/mpiexec 1:#!/bin/sh 3:/opt/mpich/bin/mpiexec "$@" /home/jed/usr/ccache/mpich/bin/mpicc 1:#!/bin/dash 3:ccache /opt/mpich/bin/mpicc "$@" /home/jed/usr/ccache/mpich/bin/mpicxx

Re: [petsc-dev] ccache tips?

2020-01-17 Thread Matthew Knepley
I configured MPI with CC="ccache gcc" knepley/feature-dm-remove-hybrid *$:/PETSc3/petsc/petsc-dev$ /PETSc3/petsc/bin/mpicc -show /Users/knepley/MacSoftware/bin/ccache gcc -Qunused-arguments -fstack-protector -Qunused-arguments -g3 -Wl,-flat_namespace -I/PETSc3/petsc/include -L/PETSc3/petsc/lib

[petsc-dev] ccache tips?

2020-01-17 Thread Patrick Sanan
I'm shamefully not using ccache. How do I do it? Is it as simple as ./configure --with-cc="ccache gcc" --with-cxx="ccache g++"? Works on OS X and various Linuxes? Any known issue with external packages or otherwise?