The ABINIT Users Mailing List ( CLOSED )

["Anglade Pierre-Matthieu" <anglade@gmail.com>]

Hi all

When the configure script fails to detect correctly something, the
best is usually to have a look at config.log.
There, you will find which commands fails and generated error
messages. This is most useful to guess what went wrong. And almost
always much more easy than direct reading of the configure script.

regards

PMA

On 9/26/07, Paul Fons <paul-fons@aist.go.jp> wrote:
>
> I suspect that you need to provide a path to the mpi environment and that is
> all, e.g.
>
> ./configure --with-mpi-prefix=/opt/openmpi
> --enable-64bit-flags
>
> works just fine in my case.  Try adding the correct prefix (note that there
> are lib, bin directories under /opt/mpi)
>
>
>  Paul
>
>
>
>
> On Sep 26, 2007, at 3:41 AM, Tobias Burnus wrote:
>
> José C. Conesa wrote:
> I have had serious difficulties in compiling parallel versions of ABINIT
> in some machines: even changing a number of parameters in the
> hostname.ac file in different ways, configure stubbornly insists in
> saying that no fortran native MPI mode is detected, and the mpi
> version is not made.
>
> I have similar problems. I would have expected that
>    ./configure --enable-mpi
> --with-mpi-fc=/usr/lib64/mpi/gcc/openmpi/bin/mpif90
> FC=gfortran
> would work, but it does not:
>
> checking for a native MPI support... no
> checking whether to build parallel code... no
>
> which is not surprising as not the MPI compiler but the normal compiler
> is used:
>
> configure:10981: gfortran -o conftest    conftest.F90  >&5
> Error: Can't open included file 'mpif.h'
>
> Note: mpif90 is at a bit strange location on openSUSE (see above) to
> allow for multiple MPI installations installed at the same time.
>
>
> At the end I was configuring once for abinis and the rest, and once for
> abinip using:
>
> ./configure FCFLAGS="-O2 `mpif90 -showme:compile`" --enable-mpi
> LDFLAGS="`mpif90 -showme:link`"
>
> (Whether -showme:* works, depends on the MPI library; I'm using OpenMPI
> which offers this option.)
>
>
> By the way, I also don't understand why there is not give YES for:
>
> configure:8697: checking if we are using the GNU Fortran compiler
> configure:8720: result: no
>
> As I use:
> $ gfortran --version|head -n1
> GNU Fortran (GCC) 4.2.1 (SUSE Linux)
>
>
> Tobias
>
>
>
>


-- 
Pierre-Matthieu Anglade