I know this isn't "recommend", but a vendor recently gave me an executable compiled openmpi-1.8.3 and I happened to have recently completed a build of 1.8.4 (but didn't have 1.8.3 sitting around and the vendor refuses to provide his build).
Since these releases are so close they should be ABI compatible so I thought I would see what happens... [arwild1@hplcslsp2 ~]$ mpirun -n 2 -H localhost vendor_app_mpi [hplcslsp2:11394] [[56032,0],0] tcp_peer_recv_connect_ack: received different version from [[56032,1],0]: 1.8.3 instead of 1.8.4 [hplcslsp2:11394] [[56032,0],0] tcp_peer_recv_connect_ack: received different version from [[56032,1],1]: 1.8.3 instead of 1.8.4 and then everything hangs. I can clearly see the output coming from ./orte/mca/oob/tcp/oob_tcp_connection.c and where it returns return ORTE_ERR_CONNECTION_REFUSED; So it looks like I'm going to have to at least build 1.8.3, but is there any way to work around this given we are dealing with builds that are that close? I'm really not interested in "rolling back" to 1.8.3 or providing both releases on my system. (yes, "right answer" is to get the vendor to provide his build... long stoy) -Alan -- a...@madllama.net http://humbleville.blogspot.com
