Todd, I've been building PETSc on Titan and SUMMIT for users. cray-petsc has been hosed for a while. I put my most recent configure file in:
/ccs/proj/env003/arch-titan-opt64idx-pgi.py This is a public space. My builds are here also. You run with, for instance, make PETSC_DIR=/ccs/proj/env003/petscv3.9-opt64-pgi PETSC_ARCH="" There are several other builds in there that you can use. I now see that I don't have the machine name in the directory name, yuck. But this and a v3.7 version are recent and work (on Titan). Mark On Fri, Jul 6, 2018 at 6:47 PM Smith, Barry F. <bsm...@mcs.anl.gov> wrote: > > I know Mark Adams has tried recently; without limited success. > > As always the big problem is facilities removing accounts, such as > Satish's, so testing gets difficult. > > But yes, we want to support Titan so have users send > configure.log/make.log to petsc-ma...@mcs.anl.gov > > Barry > > > > On Jul 6, 2018, at 12:45 PM, Munson, Todd <tmun...@mcs.anl.gov> wrote: > > > > > > Barry, > > > > Have you tested petsc compilation on titan? Is there a config example > > for that machine? > > > > Apparently titan died and when they brought it back up, the petsc install > > was fracked, so some ORNL users are trying to compile petsc locally > > rather than wait for the facilities people. > > > > Thanks, Todd > > > >