I am unable to reproduce these issues on master HEAD; assumedly they have something to do with UCX...?
I filed https://github.com/open-mpi/ompi/issues/6995 to track the issue. On Sep 19, 2019, at 11:40 AM, Jan Bierbaum via devel <devel@lists.open-mpi.org<mailto:devel@lists.open-mpi.org>> wrote: Switching on various debug options, my builds of OpenMPI with UCX fail (and his time I made sure it's not due to my own stupidity … I hope). The problematic options and respective compiler errors are '--enable-timing' Making all in mca/ess/pmi make[2]: Entering directory '/dev/shm/openmpi-4.0.2rc2/build/orte/mca/ess/pmi' CC ess_pmi_component.lo CC ess_pmi_module.lo In file included from ../../../../../orte/mca/ess/pmi/ess_pmi_module.c:57: ../../../../../orte/mca/ess/pmi/ess_pmi_module.c: In function ‘rte_init’: ../../../../../orte/mca/ess/pmi/ess_pmi_module.c:467:26: error: ‘ess_base_setup’ undeclared (first use in this function); did you mean ‘event_base_set’? OPAL_TIMING_ENV_NEXT(ess_base_setup, "state_framework_open"); ^~~~~~~~~~~~~~ ../../../../../opal/util/timings.h:103:13: note: in definition of macro ‘OPAL_TIMING_ENV_NEXT’ if( h->enabled ){ \ ^ ../../../../../orte/mca/ess/pmi/ess_pmi_module.c:467:26: note: each undeclared identifier is reported only once for each function it appears in OPAL_TIMING_ENV_NEXT(ess_base_setup, "state_framework_open"); ^~~~~~~~~~~~~~ ../../../../../opal/util/timings.h:103:13: note: in definition of macro ‘OPAL_TIMING_ENV_NEXT’ if( h->enabled ){ \ ^ make[2]: *** [Makefile:1857: ess_pmi_module.lo] Error 1 make[2]: Leaving directory '/dev/shm/openmpi-4.0.2rc2/build/orte/mca/ess/pmi' and '--enable-mem-debug' Making all in profile make[3]: Entering directory '/dev/shm/ompi/build/oshmem/shmem/c/profile' LN_S pshmem_init.c LN_S pshmem_finalize.c […] CC pshmem_put.lo CC pshmem_g.lo pshmem_free.c: In function ‘_shfree’: pshmem_free.c:65:39: error: macro "free" passed 2 arguments, but takes just 1 rc = s->allocator->free(s, ptr); ^ pshmem_free.c:65:12: warning: assignment to ‘int’ from ‘int (*)(map_segment_t *, void *)’ {aka ‘int (*)(struct map_segment *, void *)’} makes integer from pointer without a cast [-Wint-conversion] rc = s->allocator->free(s, ptr); ^ make[3]: *** [Makefile:1964: pshmem_free.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... pshmem_realloc.c: In function ‘_shrealloc’: pshmem_realloc.c:59:56: error: macro "realloc" passed 4 arguments, but takes just 2 rc = s->allocator->realloc(s, size, ptr, &pBuff); ^ pshmem_realloc.c:59:12: warning: assignment to ‘int’ from ‘int (*)(map_segment_t *, size_t, void *, void **)’ {aka ‘int (*)(struct map_segment *, long unsigned int, void *, void **)’} makes integer from pointer without a cast [-Wint-conversion] rc = s->allocator->realloc(s, size, ptr, &pBuff); ^ make[3]: *** [Makefile:1964: pshmem_realloc.lo] Error 1 make[3]: Leaving directory '/dev/shm/ompi/build/oshmem/shmem/c/profile' Preparing this report, I just noticed that the '--enable-timing' bug has already been fixed on 'master' with commit 8e7d874e14a5485dceff836419e36b6b24a66f48. Would be nice if this could make it into the 'v4.0.x' branch. Software used: - automake (GNU automake) 1.16.1 - m4 (GNU M4) 1.4.18 - autoconf (GNU Autoconf) 2.69 - libtoolize (GNU libtool) 2.4.6 - flex 2.6.4 - gcc (Debian 8.3.0-6) 8.3.0 - UCT version=1.6.1-rc2 Build process: $ git clone https://github.com/open-mpi/ompi.git $ cd ompi $ ./autogen.pl &> auto.log $ ./configure --prefix=${DIR} --with-ucx=${PATH_TO_UCX} --enable-mem-debug &> configure.log $ make -j 8 &> make.log The respective log files are attached in compressed form and, for your convenience, also available online auto.log -> https://pastebin.com/cysbi3Vx configure.log -> https://pastebin.com/rEcngh6D make.log -> https://pastebin.com/HMETcSVA Regards, Jan <logs.tar.bz2>_______________________________________________ devel mailing list devel@lists.open-mpi.org<mailto:devel@lists.open-mpi.org> https://lists.open-mpi.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com<mailto:jsquy...@cisco.com>
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
