Re: [OMPI users] [open-mpi/ompi] COMM_SPAWN broken on Solaris/v1.10 (#1569)

Hi Gilles, the minimal configuration to reproduce an error with spawn_master are two Sparc machines. tyr spawn 124 ompi_info | grep -e "OPAL repo revision" -e "C compiler absolute" OPAL repo revision: v1.10.2-176-g9d45e07 C compiler absolute: /usr/local/gcc-5.1.0/bin/gcc tyr spawn 1

Re: [OMPI users] [open-mpi/ompi] COMM_SPAWN broken on Solaris/v1.10 (#1569)

Hi Gilles, today I'm building all current versions with both compilers on my machines. Unfortunately it takes some hours, because especially my Solaris Sparc machine is old and slow. Yesterday I've had problems using two Sparc machines and nothing else. Tonight the new versions will be copied to

Re: [OMPI users] [open-mpi/ompi] COMM_SPAWN broken on Solaris/v1.10 (#1569)

Siegmar, i was unable to reproduce the issue with one solaris 11 x86_64 VM and one linux x86_64 VM what is the minimal configuration you need to reproduce the issue ? are you able to reproduce the issue with only x86_64 nodes ? i was under the impression that solaris vs linux is the issue,

Re: [OMPI users] [open-mpi/ompi] COMM_SPAWN broken on Solaris/v1.10 (#1569)

Hi Gilles, is the following output helpful to find the error? I've put another output below the output from gdb, which shows that things are a little bit "random" if I use only 3+2 or 4+1 Sparc machines. tyr spawn 127 /usr/local/gdb-7.6.1_64_gcc/bin/gdb mpiexec GNU gdb (GDB) 7.6.1 Copyright (C)

Re: [OMPI users] [open-mpi/ompi] COMM_SPAWN broken on Solaris/v1.10 (#1569)

Siegmar, is this Solaris 10 specific (e.g. Solaris 11 works fine) ( I only have a x86_64 vm with Solaris 11 and sun compilers ...) Cheers, Gilles On Thursday, May 5, 2016, Siegmar Gross < siegmar.gr...@informatik.hs-fulda.de> wrote: > Hi Ralph and Gilles, > > Am 04.05.2016 um 20:02 schrieb rh

Re: [OMPI users] [open-mpi/ompi] COMM_SPAWN broken on Solaris/v1.10 (#1569)

Hi Ralph and Gilles, Am 04.05.2016 um 20:02 schrieb rhc54: @ggouaillardet Where does this stand? — You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub