[petsc-users] problem configuring 3.8.3 with intel mpi

Klaij, Christiaan C.Klaij at marin.nl
Thu Mar 22 09:04:46 CDT 2018

Fair enough.

As a side note: if you want intel compilers, there's no need to
specify mpiicc, intel says to export I_MPI_CC=icc, which gives

$ which mpicc
$ mpicc -v
mpiicc for the Intel(R) MPI Library 2017 Update 1 for Linux*
Copyright(C) 2003-2016, Intel Corporation.  All rights reserved.
icc version 17.0.1 (gcc version 4.8.5 compatibility)

(otherwise they wrap the gnu compilers by default, baffling)


dr. ir. Christiaan Klaij  | Senior Researcher | Research & Development
MARIN | T +31 317 49 33 44 | mailto:C.Klaij at marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/Frequency-of-spill-model-for-area-risk-assessment-of-shipsource-oil-spills-in-Canadian-waters-1.htm

From: Satish Balay <balay at mcs.anl.gov>
Sent: Thursday, March 22, 2018 2:54 PM
To: Klaij, Christiaan
Cc: petsc-users
Subject: Re: [petsc-users] problem configuring 3.8.3 with intel mpi

On Thu, 22 Mar 2018, Klaij, Christiaan wrote:

> OK, configure works with the option --with-cc=/path/to/mpicc,
> thanks!
> I'm not sure you are right about checking --with-mpi-dir/bin,

There are 2 types of options to configure:
 - tell configure what to use - i.e do not guess [like --with-cc=mpicc']
 - tell configure to *guess* with partial info [like --with-package-dir=/path/to/foo/bar]

When configure has to guess - it will never be perfect.

Sure - perhaps the guessing of --with-mpi-dir can be improved - but it will never be perfect.

> because, at least with this install, the binaries are located in
> --with-mpi-dir/intel64/bin:
> $ which mpicc
> /opt/intel/compilers_and_libraries_2017.1.132/linux/mpi/intel64/bin/mpicc

So the more appropriate thing here [wrt petsc configure] is

And then - what if you want to use intel compilers and not gnu
compilers [with intel mpi]? - you have to specify mpiicc - and not
mpicc - so its best to prefer 'no-guess' options like --with-cc.
[with-mpi-dir is usually convinent - but not always suitable]


> Perhaps something to do with intel supporting both 32 and
> 64bit. Anyway, our sysadmin didn't change any of these locations,
> they just run the intel installer and this is what we got.

More information about the petsc-users mailing list