So is this the instructions that I should give him? This grad student is a
quick study but he has not computing background. So we don't care what we
use, we just want to work (easily).
Thanks
Do not use "--download-fblaslapack=1". Set it to 0. Same for
"--download-mpich=1".
Now do:
> module load mkl
> export BLAS_LAPACK_LOAD=--with-blas-lapack-dir=${MKLROOT}
> export PETSC_MPICH_HOME="${MPICH_HOME}"
And use
--with-cc=${MPICH_HOME}/mpicc --with-cxx=${MPICH_HOME}/mpicxx
--with-fc=${MPICH_HOME}/mpif90
instead of clang++
On Wed, Mar 27, 2019 at 9:30 AM Matthew Knepley <knep...@gmail.com> wrote:
> On Wed, Mar 27, 2019 at 8:55 AM Victor Eijkhout via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> On Mar 27, 2019, at 7:29 AM, Mark Adams <mfad...@lbl.gov> wrote:
>>
>> How should he configure to this? remove "--download-fblaslapack=1" and
>> add ....
>>
>>
>> 1. If using gcc
>>
>> module load mkl
>>
>> with either compiler:
>>
>> export BLAS_LAPACK_LOAD=--with-blas-lapack-dir=${MKLROOT}
>>
>> 2. We define MPICH_HOME for you.
>>
>> With Intel MPI:
>>
>> export PETSC_MPICH_HOME="${MPICH_HOME}/intel64"
>> export mpi="--with-mpi-compilers=1 --with-mpi-include=${TACC_IMPI_INC}
>> --with-mpi-lib=${TACC_IMPI_LIB}/release_mt/libmpi.so”
>>
>> with mvapich:
>>
>> export PETSC_MPICH_HOME="${MPICH_HOME}"
>> export mpi="--with-mpi-compilers=1 --with-mpi-dir=${PETSC_MPICH_HOME}”
>>
>> (looks like a little redundancy in my script)
>>
>
> I think Satish now prefers
>
> --with-cc=${MPICH_HOME}/mpicc --with-cxx=${MPICH_HOME}/mpicxx
> --with-fc=${MPICH_HOME}/mpif90
>
> Thanks,
>
> Matt
>
>
>> Victor.
>>
>>
>
> --
> 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
>
> https://www.cse.buffalo.edu/~knepley/
> <http://www.cse.buffalo.edu/~knepley/>
>
