[MTT users] OMPI snapshot tarball generation
FYI -- see: http://www.open-mpi.org/community/lists/devel/2006/08/1015.php This means that MTT will potentially have to test less stuff. More specifically, MTT will only have a tarball to test when there is actually something new to test. Hence, this can significantly decrease the proability of their being 1.1 and 1.0 tarballs to test, and therefore lower the amount of resources required for sites to test 1.1 and 1.0. We used to generate new tarballs for all branches whenever there was even one commit on any development/release. -- Jeff Squyres Server Virtualization Business Unit Cisco Systems
[OMPI users] OpenMPI error in the simplest configuration...
Hi all I am getting an error (details follow) in the simplest of the possible test scenarios: Two identical regular Dell PCs connected back-to-back via an ethernet switch on the 10/100 ethernet. Both run Fedora Core 4. Identical version (1.1) of Open MPI is compiled and installed on both of them *without* a --prefix option (i.e. installed on the default location of /usr/local). The hostfile on both the machine is the same: cat ~/hostfile 192.168.22.29 192.168.22.103 I can run openMPI on either of these two machines by forking two processes: mpirun -np2 osu_acc_latency <-- This runs fine on either of the two machines. However, when I try to luch the same program across the two machines, I get an error: mpirun --hostfile ~/hostfile -np2 /home/durga/openmpi-1.1 /osu_benchmarks/osu_acc_latency durga@192.168.22.29's password: foobar /home/durga/openmpi-1.1/osu_benchmarks/osu_acc_latency: error while loading shared libraries: libmpi.so.0: cannot open shared object file: No such file or directory. However, the file *does exist* in /usr/local/lib: ls -l /usr/local/lib/libmpi.so.0 libmpi.so.0 -> libmpi.so.0.0.0 I have also tried adding /usr/local/lib to my LD_LIBRARY_PATH on *both* machines, to no avail. Any help is greatly appreciated. Thanks Durga
[OMPI users] Problems with symbols and shared libraries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I am trying to get OpenMPI 1.1 to run on an SGI Altix 4700 (with SLES10). A trivial Fortran 90 application using MPI_Wtime() does not link: mpif90 -g -o runhost.exe runhost.o /lrz/sys/openmpi/intel_altix_mt/1.1/lib/libmpi_f90.a(mpi_wtime_f90.o): In function `mpi_wtime_': mpi_wtime_f90.f90:(.text+0x22): undefined reference to `mpi_wtime_f90_' it appears the default linkage uses the static libraries. If the "-shared" switch is added, linkage is successful, but execution fails, sometimes silently with an exit status of 139, sometimes with the additional message 1 additional process aborted (not shown) The compiler releases used: ifort 9.1.33, icc 9.1.39 I am attaching a UNIX archive with build info. A second archive with configure and install info as well as ompi_info output follows with a separate mail (100 kByte limit exceeded otherwise). Any hints? [Note: I've also tried building the most up to date SVN tree, but this fails since the Fortran 90 module build attempts to generate a shared library; the -soname switch used is not accepted by Intel Fortran. Trying to build with static libraries only works, but mpirun then fails with the message "You must use mpirun to start up MPI programs."] Regards - -- Dr. Reinhold Bader Leibniz-Rechenzentrum, Abt. Hochleistungssysteme | Tel. +49 89 35831 8825 Boltzmannstr. 1, 85748 Garching | Fax +49 89 35831 9700 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE8aCfzwkB8vcRvCoRAv52AJ9t7xt++pbhSoIoUWzWrSBHk8+9wACfUDDn mIo/DqAZt6VvifrhaEAkFBk= =xFBm -END PGP SIGNATURE- openmpi_pmr_1.tar.bz2 Description: Unix tar archive
