Re: [OMPI users] Alpha system & OpenMPI 1.2.1 does not work...

2007-05-01 Thread Rob
Rob wrote at 2007-05-01 21:11:26 : > I'm now trying the nightly build from SVN > (version 1.3a1r14551), but I'm afraid that Alpha > support is still not there.if that's the case, > is there any chance to fix openmpi for Alpha? Indeed this fails with the same error as the compilation of 1.2.1

[OMPI users] Alpha system & OpenMPI 1.2.1 does not work...

2007-05-01 Thread Rob
Hi, A few emails back I reported that I could build openmpi on Alpha system (except the static libraries). However, it seems that the built result is unusable. With every simple program (even non-mpi) I compile, I get: $ mpicc myprog.c --showme:version mpicc: Open MPI 1.2.1 (Language: C)

Re: [OMPI users] Torque and OpenMPI 1.2.1 problems

2007-05-01 Thread Ole Holm Nielsen
Thanks for the suggestion. I inserted a printenv command and the path and library variables seem to be correct for our OpenMPI installation: LD_LIBRARY_PATH=/usr/local/openmpi-1.2.1-pgi/lib:/opt/intel/compiler90/lib MPIHOME=/usr/local/openmpi-1.2.1-pgi PATH=/usr/local/openmpi-1.2.1-pgi/bin:/usr/

Re: [OMPI users] Torque and OpenMPI 1.2.1 problems

2007-05-01 Thread Ralph Castain
The most likely problem is that you have a path or library issue regarding the location of the OpenMPI/OpenRTE executables when running batch versus interactive. We see this sometimes when the shell startups differ in those two modes. You might try just running a batch vs interactive printenv to s

Re: [OMPI users] OpenMPI 1.2.1: "configure --enable-static": then make ends with error

2007-05-01 Thread Rob
Brian Barrett wrote on 2007-05-01 10:58:45 : > Can you send the information requested here: > http://www.open-mpi.org/community/help/ > That should help us figure out what happened. Thank you for the quick response. The output files together are over 100 kB, so I can't send them as attachment t

Re: [OMPI users] OpenMPI 1.2.1: "configure --enable-static": then make ends with error

2007-05-01 Thread Brian Barrett
That is odd... Alpha Linux isn't one of our supported platforms, so it doesn't get tested before release unless a user happens to try it. Can you send the information requested here: http://www.open-mpi.org/community/help/ That should help us figure out what happened. Thanks, Brian On

[OMPI users] Torque and OpenMPI 1.2.1 problems

2007-05-01 Thread Ole Holm Nielsen
We have built OpenMPI 1.2.1 with support for Torque 2.1.8 and its Task Manager interface. We use the PGI 6.2-4 compiler and the --with-tm option as described in http://www.open-mpi.org/faq/?category=building#build-rte-tm for building an OpenMPI RPM on a Pentium-4 machine running CentOS 4.4 (RHEL4

Re: [OMPI users] MPI_Comm_Accept / MPI::Comm::Accept problem.

2007-05-01 Thread Jeff Squyres
For the moment, a possible workaround might be to use plain TCP sockets (i.e., outside of MPI) to make the initial connection. That way, you can just have your server blocking in accept(). After the TCP connection is made, use MPI_COMM_JOIN to create a communicator and then proceed with no

Re: [OMPI users] OpenMPI 1.2.1: "configure --enable-static": then make ends with error

2007-05-01 Thread Jeff Squyres
Brian -- Is this due to missing assembly functionality for Alpha platforms in opal? (I'm not sure why it would work with dynamic if that were the case, though...) On May 1, 2007, at 6:41 AM, Rob wrote: Hi all, I use gcc-4.1.3 (gcc/g++/gfortran) with openmpi-1.2.1 on an Alpha system

[OMPI users] OpenMPI 1.2.1: "configure --enable-static": then make ends with error

2007-05-01 Thread Rob
Hi all, I use gcc-4.1.3 (gcc/g++/gfortran) with openmpi-1.2.1 on an Alpha system with Linux CentOS 4.4. The "--enable-static" configure option causes the make to end with error. Without this configure option, there is no problem with the make. Note that I need the "-mfp-trap-mode=su" compiler fl