Hello,
I am trying to run a program on a cluster composed with Apple Xserve running
10.5.8 (Leopard).
1) I am using openmpi-1.4.4 compiled with Intel ifort and icc (V12)
(/opt is a share point mounted in /Network/opt with NFS)
./configure --prefix=/opt/openmpi-1.4.4
On Nov 7, 2011, at 12:12 PM, Blosch, Edwin L wrote:
> Thanks for the valuable input. I'll change to a wait-and-watch approach.
>
> The FAQ on tuning sm says "If the session directory is located on a network
> filesystem, the shared memory BTL latency will be extremely high." And the
> title is
The problem is that the prefix you configured with doesn't match the prefix you
are providing:
configure: prefix = /opt/openmpi-1.4.4
running: prefix = /Network/opt/openmpi-1.4.4
The two have to match in order for the libraries to be found.
On Nov 8, 2011, at 6:01 AM, Christophe Peyret wrot
We talked about this issue on the weekly OMPI engineering teleconf today.
It seems like it would be a good idea to bring over the new shared memory
revamp to the v1.5 series before it transitions to v1.6 so that it can avoid
network-mounted /tmp filesystem issues. LANL will be evaluating this;
I'm attempting to launch my app via mpirun and a host file to use nodes on
multiple 'stand-alone' servers. mpirun is able to launch my app on all
requested nodes on all servers, but my app doesn't seem to be able to
communicate via the standard MPI api calls (send , recv, etc). The
problem se
Dear OpenMPI pros
When I try to build OpenMPI 1.4.4 with PGI compilers 11.7 [pgcc, pgcc,
pgfortran]
I get the awkward error message on the bottom of this email.
I say awkward because I assigned the value 'shanghai-64' to the '-tp' flag,
as you can see from the successful 'libtool:compile' comman
Hi,
I think I've seen this before.
I can't speak to the details surrounding this issue, but when I upgraded to the
newest version of libtool, the problem went away .
Take a look at "Use of GNU m4, Autoconf, Automake, and Libtool" in our HACKING
file. libtool-2.4.2.tar.gz **should** work, if t
Thank you, Samuel
I was hoping not to have to change my Gnu auto tools in the cluster.
I remain a bit skeptical that libtool is the main culprit.
Somehow OpenMPI 1.4.3 builds fine in the very same computer
with the same libtool, same PGI 11.7, same compiler flags.
In the OMPI 1.4.3 make log there
Folks,
Wednesday November 15th at 12:15 PST, we will have an Open MPI BOF. We will
have two guest speakers: Rolf vandeVaart from NVIDIA and Shinji Sumimoto from
the K-computer. If you are at SC, you are all invited to participate to this
annual event. Blend for a moment with our user community,
Sam --
The production tarballs are pre-Autotools-bootstrapped; the end user doesn't
even have to have the GNU autotools installed at all. As such, it doesn't
matter what version of OMPI they have installed.
On Nov 8, 2011, at 4:24 PM, Samuel K. Gutierrez wrote:
> Hi,
>
> I think I've seen
It looks like we added a patch to the libtool bootstrap in the 1.4.4 tarball
(because we're using a quite old version of Libtool to build that tarball) in
r24224:
https://svn.open-mpi.org/trac/ompi/changeset/24224
This was to close CMR https://svn.open-mpi.org/trac/ompi/ticket/2670, which w
11 matches
Mail list logo
