Re: [OMPI devel] [3.0.0rc1] ppc64/gcc-4.8.3 check failure (regression).

2017-07-03 Thread Kawashima, Takahiro
It might be related to https://github.com/open-mpi/ompi/issues/3697 . I added a comment to the issue. Takahiro Kawashima, Fujitsu > On a PPC64LE w/ gcc-7.1.0 I see opal_fifo hang instead of failing. > > -Paul > > On Mon, Jul 3, 2017 at 4:39 PM, Paul Hargrove wrote: > > > On a PPC64 host with

[OMPI devel] [3.0.0rc1] PMIX ERROR: UNPACK-INADEQUATE-SPACE

2017-07-03 Thread Paul Hargrove
On (at least) two different hosts (both Linux, one x86-64 and one ppc64el) I am seeing a failure to launch ring_c with errors like those shown below. -Paul $ mpirun -mca btl sm,self -np 2 examples/ring_c [pcp-d-1:02255] PMIX ERROR: UNPACK-INADEQUATE-SPACE in file /home/phargrov/OMPI/openmpi-3.0.0

Re: [OMPI devel] [3.0.0rc1] ILP32 build failures

2017-07-03 Thread Gilles Gouaillardet
Thanks Paul, i made https://github.com/open-mpi/ompi/pull/3802 to fix this issue. once it completes CI, i will merge and PR vs the release branches Cheers, Gilles On 7/4/2017 8:19 AM, Paul Hargrove wrote: Below is the corresponding failure at build time (rather than link time) for "clang

Re: [OMPI devel] [3.0.0rc1] ppc64/gcc-4.8.3 check failure (regression).

2017-07-03 Thread Paul Hargrove
On a PPC64LE w/ gcc-7.1.0 I see opal_fifo hang instead of failing. -Paul On Mon, Jul 3, 2017 at 4:39 PM, Paul Hargrove wrote: > On a PPC64 host with gcc-4.8.3 I have configured with > > --prefix=[...] --enable-debug \ > CFLAGS=-m64 --with-wrapper-cflags=-m64 \ > CXXFLAGS=-m64 --with-wrapper-cx

[OMPI devel] [3.0.0rc1] ppc64/gcc-4.8.3 check failure (regression).

2017-07-03 Thread Paul Hargrove
On a PPC64 host with gcc-4.8.3 I have configured with --prefix=[...] --enable-debug \ CFLAGS=-m64 --with-wrapper-cflags=-m64 \ CXXFLAGS=-m64 --with-wrapper-cxxflags=-m64 \ FCFLAGS=-m64 --with-wrapper-fcflags=-m64 I see "make check" report a failure from opal_fifo. Previous testing of Open MPI 2.

Re: [OMPI devel] [3.0.0rc1] ILP32 build failures

2017-07-03 Thread Paul Hargrove
Below is the corresponding failure at build time (rather than link time) for "clang -m32" on Linux/x86-64. -Paul libtool: compile: clang -DHAVE_CONFIG_H -I. -I/scratch/phargrov/OMPI/openmpi-3.0.0rc1-linux-x86_64-clang-m32/openmpi-3.0.0rc1/opal -I../opal/include -I../ompi/include -I../oshmem/incl

[OMPI devel] [3.0.0rc1] XLC build error

2017-07-03 Thread Paul Hargrove
With xlc-12.1 and 13.1 (big-endian PPC64, both LP64 and ILP32) there are numerous problems compiling with ompi_datatype_module.c (a prefix of which are shown below). -Paul libtool: compile: xlc -DHAVE_CONFIG_H -I. -I/home/hargrove/SCRATCH/OMPI/openmpi-3.0.0rc1-linux-ppc32-xlc-12.1/openmpi-3.0.0

[OMPI devel] [3.0.0rc1] ILP32 build failures

2017-07-03 Thread Paul Hargrove
On every ILP32 build I try w/ gcc, I get the following. ../../../opal/.libs/libopen-pal.so: undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status make[2]: *** [opal_wrapper] Error 1 This includes at least x86 and ppc32 (probably MIPS and ARM, but those are too s

Re: [OMPI devel] Use of gethostbyname

2017-07-03 Thread Gilles Gouaillardet
Thanks Philipp, You can open a Pull Request vs the master branch on the github repository https://github.com/open-mpi/ompi.git All you need is sign-off your commits (please make sure you understand what it means) Then one of us will backport it to the release branches once it gets merged. Cheer

[OMPI devel] Use of gethostbyname

2017-07-03 Thread Philipp Thomas
When packaging openMPI 3.0.0rc1 I get two warnings: [ 280s] openmpi3-libs.x86_64: I: binary-or-shlib-calls-gethostbyname /usr/lib64/mpi/gcc/openmpi3/lib64/libopen-rte.so.40.0.0 [ 280s] openmpi3-devel.x86_64: I: binary-or-shlib-calls-gethostbyname /usr/lib64/mpi/gcc/openmpi3/lib64/openmpi/mca_