http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19174 <pre> No, not even if they use mpif.h. Here's a chunk of text from the v1.6 README: - While it is possible -- on some platforms -- to configure and build Open MPI with one Fortran compiler and then build MPI applications with a different Fortran compiler, this is not recommended. Subtle problems can arise at run time, even if the MPI application compiled and linked successfully. Specifically, the following two cases may not be portable between different Fortran compilers: 1. The C constants MPI_F_STATUS_IGNORE and MPI_F_STATUSES_IGNORE will only compare properly to Fortran applications that were created with Fortran compilers that that use the same name-mangling scheme as the Fortran compiler with which Open MPI was configured. 2. Fortran compilers may have different values for the logical .TRUE. constant. As such, any MPI function that uses the Fortran LOGICAL type may only get .TRUE. values back that correspond to the the .TRUE. value of the Fortran com</pre> Jeff Squyres (jsquyres 2013-05-25T12:26:44 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19173 <pre>It sounds like your saying that the OMPI trunk replicates the same behavior you reported elsewhere - which isn't a surprise. Let's track this on your prior messages as the two problems are not related. On May 24, 2013, at 12:28 AM, Siegmar Gross &lt;Siegmar.Gross&lt; at &gt;informatik.hs-fulda.de&gt; wrote: </pre> Ralph Castain 2013-05-24T14:14:51 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19172 <pre>Could you please clarify - are you mixing 32 and 64 bit versions in your runs that have a problem? If so, then I doubt that would work, so please check. If that isn't the case, then the error message is telling you that the system thinks you are mixing optimized and debug versions - i.e., one node is using an optimized version of OMPI and another is using a debug version. This also isn't allowed. If you check and find those two conditions are okay, then I suspect you are hitting the Solaris "bit rot" problem that we've talked about before - and are unlikely to be able to fix any time soon. On May 24, 2013, at 12:02 AM, Siegmar Gross &lt;Siegmar.Gross&lt; at &gt;informatik.hs-fulda.de&gt; wrote: </pre> Ralph Castain 2013-05-24T14:12:46 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19171 <pre>Hi I installed openmpi-1.9r28534 on "openSuSE Linux 12.1", "Solaris 10 x86_64", and "Solaris 10 sparc" with "Sun C 5.12" in 32- and 64-bit versions. Unfortunately I have two problems with this version. sunpc1 hello_1 104 mpiexec -np 3 -host sunpc1,linpc1,rs0 hostname [sunpc1:18681] [[19223,0],0] ORTE_ERROR_LOG: Data unpack had inadequate space in file ../../../../openmpi-1.9r28534/orte/mca/plm/base/plm_base_launch_support.c at line 854 sunpc1 hello_1 105 which mpiexec /usr/local/openmpi-1.9_64_cc/bin/mpiexec sunpc1 hello_1 106 My second problem is, that "rank_files" don't work as expected. sunpc1 rankfiles 108 mpiexec -report-bindings \ -rf rf_ex_sunpc_linpc hostname --------------------------------------------------------------------- The rankfile that was used claimed that a host was either not allocated or oversubscribed its slots. Please review your rank-slot assignments and your host allocation to ensure a proper match. Also, some systems may require using full hostnames, such as "hos</pre> Siegmar Gross 2013-05-24T07:28:15 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19170 <pre>Hi I installed openmpi-1.7.2rc3r28550 on "openSuSE Linux 12.1", "Solaris 10 x86_64", and "Solaris 10 sparc" with "Sun C 5.12" in 32- and 64-bit versions. Unfortunately "rank_files" don't work as expected. sunpc1 rankfiles 109 more rf_ex_sunpc_linpc # mpiexec -report-bindings -rf rf_ex_sunpc_linpc hostname rank 0=linpc1 slot=0:0-1,1:0-1 rank 1=sunpc1 slot=0:0-1 rank 2=sunpc1 slot=1:0 rank 3=sunpc1 slot=1:1 sunpc1 rankfiles 110 mpiexec -report-bindings \ -rf rf_ex_sunpc_linpc hostname --------------------------------------------------------------------- The rankfile that was used claimed that a host was either not allocated or oversubscribed its slots. Please review your rank-slot assignments and your host allocation to ensure a proper match. Also, some systems may require using full hostnames, such as "host1.example.com" (instead of just plain "host1"). Host: linpc1 --------------------------------------------------------------------- sunpc1 rankfiles 111 sunpc1 rankfiles 111 which mpiexec /usr/</pre> Siegmar Gross 2013-05-24T07:16:52 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19169 <pre>Hi I installed openmpi-1.6.5a1r28554 on "openSuSE Linux 12.1", "Solaris 10 x86_64", and "Solaris 10 sparc" with gcc-4.8.0 and "Sun C 5.12" in 32- and 64-bit versions. Unfortunately I have a problem with the 64-bit version, if I build Open MPI with gcc. The program hangs and I have to terminate it with &lt;Ctrl-c&gt;. sunpc1 hello_1 144 mpiexec -mca btl ^udapl -np 4 \ -host sunpc1,linpc1,rs0 hello_1_mpi [sunpc1:15576] [[16182,0],0] ORTE_ERROR_LOG: Buffer type (described vs non-described) mismatch - operation not allowed in file ../../../../../openmpi-1.6.5a1r28554/orte/mca/grpcomm/bad/grpcomm_bad_module.c at line 841 ^Cmpiexec: killing job... sunpc1 hello_1 145 which mpiexec /usr/local/openmpi-1.6.5_64_gcc/bin/mpiexec sunpc1 hello_1 146 I have no problems with the 64-bit version, if I compile Open MPI with Sun C. Both 32-bit versions (compiled with "cc" or "gcc") work as expectedas well. sunpc1 hello_1 106 mpiexec -mca btl ^udapl -np 4 \ -host sunpc1,linpc1,rs0 hello_1_mpi Process 2 of 4 running o</pre> Siegmar Gross 2013-05-24T07:02:52 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19168 <pre>Excellent. Now I've read the FAQ and noticed that it doesn't mention the issue with the Fortran 90 .mod signatures. Our applications are Fortran. So your replies are very helpful -- now I know it really isn't practical for us to use the default OpenMPI shipped with RHEL6 since we use both Intel and PGI compilers and have several applications to accommodate. Presumably if all the applications did INCLUDE 'mpif.h' instead of 'USE MPI' then we could get things working, but it's not a great workaround. Thank you very much ________________________________________ From: users-bounces&lt; at &gt;open-mpi.org [users-bounces&lt; at &gt;open-mpi.org] on behalf of Tim Prince [n8tm&lt; at &gt;aol.com] Sent: Wednesday, May 22, 2013 10:24 AM To: users&lt; at &gt;open-mpi.org Subject: EXTERNAL: Re: [OMPI users] basic questions about compiling OpenMPI On 5/22/2013 11:34 AM, Paul Kapinos wrote: The gfortran build of Fortran library, as well as the .mod USE files, won't work with ifort or PGI compilers. g++ built libraries ought to work with sufficiently recen</pre> Blosch, Edwin L 2013-05-23T13:50:20 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19167 <pre> Ok, sorry about that! thanks for the historical and technical informations! Eric </pre> Eric Chamberland 2013-05-22T17:40:39 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19166 <pre>I was afraid that was the case. Too bad, because applications (and the files they use), are getting much too big for the 32 bit limit. T. Rosmond On Wed, 2013-05-22 at 09:37 -0700, Ralph Castain wrote: </pre> Tom Rosmond 2013-05-22T16:47:40 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19165 <pre> On May 22, 2013, at 9:23 AM, Eric Chamberland &lt;Eric.Chamberland&lt; at &gt;giref.ulaval.ca&gt; wrote: Well, ROMIO was written by Argonne/MPICH (unfair to point the finger solely at Rob) and picked up by pretty much everyone. The issue isn't a bug in MPIIO, but rather in the MPI functional descriptions. They stipulate that the input param be an int, which defaults to 32-bits on the described system. So there is no way to reference anything beyond 32-bits in size. Afraid you'll have to do the multiple reads, or switch to a system that defaults to 64-bit integers. </pre> Ralph Castain 2013-05-22T16:37:57 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19164 <pre> We’re seeing some abnormal performance behavior when running an OpenMPI 1.4.4 application on RH6.4 using Mellanox OFED 1.5.3. Under certain circumstances, system CPU starts dominating and performance tails off severely. This behavior does not happen with the same job run with TCP. Is there a resource that shows what’s compatible with what? For example, does OpenMPI need to be rebuilt when an OFED changes, etc? _______________________________________________ users mailing list users&lt; at &gt;open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users</pre> BRADLEY, PETER C PW 2013-05-22T16:26:38 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19163 <pre>The gfortran build of Fortran library, as well as the .mod USE files, won't work with ifort or PGI compilers. g++ built libraries ought to work with sufficiently recent versions of icpc. As noted above, it's worth while to rebuild yourself, even if you use a (preferably more up to date version of) gcc, which you can use along with one of the commercial Fortran compilers for linux. </pre> Tim Prince 2013-05-22T16:24:28 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19162 <pre> I think but I am not sure that it is because the MPI I/O (ROMIO) code is the same for all distributions... It has been written by Rob Latham. Maybe some developers could confirm this? Eric </pre> Eric Chamberland 2013-05-22T16:23:36 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19161 <pre> No comments =) At least, the Fortran-90 bindings ("use mpi") won't work at all (they're compiler-dependent. So, our way is to compile a version of Open MPI with each compiler. I think this is recommended. Note also that the version of Open MPI shipped with Linux is usuallu a bit dusty. </pre> Paul Kapinos 2013-05-22T15:34:12 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19160 <pre>If you are only using the C API there will be no issues. There are no guarantees with C++ or fortran. -Nathan Hjelm HPC-3, LANL On Wed, May 22, 2013 at 03:08:31PM +0000, Blosch, Edwin L wrote: </pre> Nathan Hjelm 2013-05-22T15:27:02 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19159 <pre>I have experienced the same problem.. and worst, I have discovered a bug in MPI I/O... look here: http://trac.mpich.org/projects/mpich/ticket/1742 and here: http://www.open-mpi.org/community/lists/users/2012/10/20511.php Eric On 05/21/2013 03:18 PM, Tom Rosmond wrote: </pre> Eric Chamberland 2013-05-22T15:21:01 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19158 <pre>Apologies for not exploring the FAQ first. If I want to use Intel or PGI compilers but link against the OpenMPI that ships with RedHat Enterprise Linux 6 (compiled with g++ I presume), are there any issues to watch out for, during linking? Thanks, Ed </pre> Blosch, Edwin L 2013-05-22T15:08:31 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19157 <pre>dmtcp is in the trunk; it didn't make it to v1.7. On May 21, 2013, at 4:34 PM, Orion Poplawski &lt;orion&lt; at &gt;cora.nwra.com&gt; wrote: </pre> Jeff Squyres (jsquyres 2013-05-21T22:30:15 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19156 <pre>You should probably post your question over on the devel list; this list is more for user-level questions about using Open MPI. On May 21, 2013, at 6:12 PM, jhonatan alves &lt;jhonatanalves1&lt; at &gt;gmail.com&gt; wrote: </pre> Jeff Squyres (jsquyres 2013-05-21T22:15:37 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19155 <pre>Sorry, we wanted to say We are trying port Open MPI.... Initially we tried to port MPICH but the OS developer suggested that we port Open MPI because there is an old port of MPICH. Thanks. 2013/5/21 jhonatan alves &lt;jhonatanalves1&lt; at &gt;gmail.com&gt; _______________________________________________ users mailing list users&lt; at &gt;open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users</pre> jhonatan alves 2013-05-21T22:12:20 http://permalink.gmane.org/gmane.comp.clustering.open-mpi.user/19154 <pre>Hello, We are trying port MPICH to a new operating system, called EPOS, but our main problem at the moment is that this operating system is not POSIX compatible. Our question is there some way to know what are the OS dependencies of Open MPI? Is there a porting manual of Open MPI? Is there a documentation for ORTE and OPAL? Thanks. _______________________________________________ users mailing list users&lt; at &gt;open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/users</pre> jhonatan alves 2013-05-21T22:09:17 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.clustering.open-mpi.user