[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ML with OpenMPI
- To: petsc-dev@xxxxxxxxxxx
- Subject: Re: ML with OpenMPI
- From: Jed Brown <jed@xxxxxxxx>
- Date: Sat, 22 Mar 2008 00:01:01 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:sender; bh=265VAvKpn9oTKZqoSu7cxm5BSCpnESsixoPXXFunZdM=; b=PwY/7DgsHg8thU45bvUANsanEygvDJDXGjocnpUj+lHsgMxBFwiYD1hU1VvxDcEXfISvvxd0f4cg3Rajx9eF+LFo6PF5SOJ7oiqaJgt+ooxlnLtJU2Gkd0/cCeR0ghpeXkn1UnpuOzTNVuWW5G+rkkoBu1+osU4k6wuOqqb+pVc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=date:from:to:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent:sender; b=jEgQ1z9HO4zhPrMA6aMp3Wjj5ChOhOv8CJwe+EotnE1nqT4ypK8h30kaFxrUmt4tplFIbDNmWIAkPmXWIbGoBi6o5f+siMNb2lMp/mNlSHKxsgUyNB778zgn/SGlVwMHh0LyJgfNF5DubF5Zq47surSgs/AqIhLRjfye9dggNuU=
- In-reply-to: <e7ba66e40803211531y566699e2maced8f5e1a15771f@mail.gmail.com>
- Mail-followup-to: petsc-dev@xxxxxxxxxxx
- References: <20080321220939.GA3976@brakk.ethz.ch> <e7ba66e40803211531y566699e2maced8f5e1a15771f@mail.gmail.com>
- Reply-to: petsc-dev@xxxxxxxxxxx
- Sender: owner-petsc-dev@xxxxxxxxxxx
- User-agent: Mutt/1.5.17 (2007-11-01)
On Fri 2008-03-21 19:31, Lisandro Dalcin wrote:
> Mmm... I believe this is a configuration issue... if ML_MPI were
> defined, then ML_USR_COMM should be MPI_Comm. But the problem is
> perhaps on the ML side, not the PETSc side.
>
> "ml_common.h" #define ML_MPI if macro HAVE_MPI is defined. In turn
> HAVE_MPI is at "ml_config.h", and that file is surelly generated by ML
> configure script. For some reason ML's configure failed to found MPI
> with the command line stuff PETSc pass to it. Look at the
> 'config.log' file inside the "ml-5.0" dir to find what happened.
From the ML docs, it looks like ML's configure expects --with-mpi-compilers if it
is building with MPI. I modified config/PETSc/packages/ml.py to include this
option and I'll let you know if it fixes the problem.
Jed
Attachment:
pgpqbhOnmDbPS.pgp
Description: PGP signature