[petsc-users] What is "You must specify a path for MPI with --with-mpi-dir=<directory>"

[Barry Smith]

  Do not use any of these options -download-mpicc=1 –download-f2cblaslapack=1   –download-f-blas-lapack=1

  Send the resulting configure.log again if it fails.

   Also we recommend installing the latest version of PETSc instead of this old one.

   Barry

On Sep 30, 2014, at 6:20 PM, Nan Zhang <Nan.Zhang at colorado.edu> wrote:

> Hi there,
> 
> I am trying to install petsc with its own mpicc. I download it and untar it under my directory. I export PETSC_DIR=`pwd` and export PETSC_ARCH=x86_64.
> 
> When I do configure:
> ./config/configure.py –with-shared-libraries=1 –with-x=0 –with-mpi=1 -download-hypre=1 –download-f-blas-lapack=1 –download-mpich=1 -download-mpicc=1 –download-f2cblaslapack=1
> 
> I got an error report:
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> The version of PETSc you are using is out-of-date, we recommend updating to the new release
>  Available Version: 3.5.2   Installed Version: 3.4.2
> http://www.mcs.anl.gov/petsc/download/index.html
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ===============================================================================
>              Configuring PETSc to compile on your system
> ===============================================================================
> TESTING: check from config.libraries(config/BuildSystem/config/libraries.py:145)                              *******************************************************************************
>          UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for details):
> -------------------------------------------------------------------------------
> You must specify a path for MPI with --with-mpi-dir=<directory>
> If you do not want MPI, then give --with-mpi=0
> You might also consider using --download-mpi instead
> *******************************************************************************
> How to solve this? I also attach my configure.log below.
> 
> Thanks!
> Nan
> <configure.log>