Just to jump in on the side of Fortran here: The statement ordering
rules are indeed sensible. You need to have your implicit typing set
before you start declaring stuff (so include must come after implicit).
You need to have all your modules used before setting your implicit
typing (as modules o
See that FAQ entry I pointed to.
${includedir} is the default "include" directory that came in from
running OMPI's configure (defaults to $prefix/include). Likewise for $
{libdir}; it's the "library" directory that came in from running
OMPI's configure (defaults to $prefix/lib).
On Sep 2
In mpic++_wrapper-data.txt what do the following statments mean and where do
they exactly point to??
--
includedir=${includedir}
libdir=${libdir}
--
--- On Tue, 9/23/08, Jeff Squyres wrote:
From: Jeff Squyres
Subject: Re: [OMPI users] where is mpif.h ?
To: "Open MPI Users"
L
Hi Brian and list
Terry Frankcombe is right on the spot on that recommendation to you.
Just to support Terry's suggestion, here is what "Fortran 95/2003
Explained", by Michael Metcalf,
John Reid, and Malcolm Cohen, Oxford Univ. Press, 2004, pp. 144, Section
7.10, says about it:
"Any 'use' s
Hello Sofia,
Very puzzling indeed. Can your try to run hostname or uptime with
mpirun? That is something like:
mpirun -np 2 --host 10.1.10.208,10.1.10.240 --mca mpi_preconnect_all 1
--prefix /usr/local -mca btl self,tcp -mca btl_tcp_if_include eth1 hostname
--td
List-Post: users@lists.o
ok now. Thanks
2008/9/23 Santolo Felaco
> Hi,
> I would like to install openmpi-1.3a1r19602, I have invoked ./autogen.sh,
> This is the error:
>
> [Running] autom4te --language=m4sh ompi_get_version.m4sh -o
> ompi_get_version.sh
> [Running] libtoolize --automake --copy --ltdl
> ls: impossibile a
Hi,
I would like to install openmpi-1.3a1r19602, I have invoked ./autogen.sh,
This is the error:
[Running] autom4te --language=m4sh ompi_get_version.m4sh -o
ompi_get_version.sh
[Running] libtoolize --automake --copy --ltdl
ls: impossibile accedere a libltdl/*: Nessun file o directory
libtoolize: c
Hello Terry,
Here you can find the files.
Thank you very much.
Sofia
- Original Message -
From: "Terry Dontje"
To:
Sent: Tuesday, September 23, 2008 4:23 PM
Subject: Re: [OMPI users] Problem with MPI_Send and MPI_Recv
Hello Sofia,
After talking with another OMPI member can you h
Hello Sofia,
After talking with another OMPI member can you humor me and do
"/sbin/iptables -L" on both your machines. You'll need to be root to
do such.
--td
List-Post: users@lists.open-mpi.org
Date: Tue, 23 Sep 2008 06:02:30 -0400
From: Terry Dontje
Subject: Re: [OMPI users] Problem with M
I am happy to report that my build of openMPI is now fully functional,
using INCLUDE "mpif.h". I have compiled and run my production code,
and it even looks to be slightly faster than when I utilize MPICH2.
Once again, I'd like to thank you guys for your help! I can't even
remember the last time
It actually is expected behavior. Open MPI's wrappers do not
automatically add -I for /usr/include or -L for /usr/lib because these
directories are typically in the compiler's/linker's default search
path, and having the wrapper compilers manually add them tends to
screw up search ordering
It's not entirely clear from the later messages whether you got it
running with mpif.h or "use mpi".
What is the source code around the problematic line when you "use
mpi"? (including all the declarations of the arguments, etc.)
MPICH2's F90 module is a bit different than ours -- I don't r
On Tue 2008-09-23 08:50, Simon Hammond wrote:
> Yes, it should be there.
Shouldn't the path be automatically included by the mpif77 wrapper? I
ran into this problem when building BLACS (my default OpenMPI 1.2.7
lives in /usr, MPICH2 is at /opt/mpich2). The build tries
$ /usr/bin/mpif90 -c -I.
Hello Sofia, Looking at your stack trace it is what I thought was
happening and that is one process is stuck trying to connect to the
other. The stack unfortunately does not give enough information as to
why. The only suggestion I could give is walk through a debuggable
version of the code from
Yes, it should be there.
Have you configured OpenMPI with Fortran during the build?
Si Hammond
High Performance Systems Group
University of Warwick
Coventry, UK
2008/9/23 Shafagh Jafer :
> Does openmpi have any "mpif.h" ?? if yes, where? in openmpi_dir/include ??!!
>
>
15 matches
Mail list logo