I have determined that 1.8.5 also fails in the same manner on this host. Configuring with --disable-io-romio allows 1.8.6rc1 to build correctly. So, the problem appears to be in ROMIO as it relates to OpenBSD-5.7.
Since this is *not* a regression I feel this should not delay a 1.8.6 release unless there is an existing fix upstream in romio. A quick look at their trac didn't show anything promising. Notice the following difference in the configure output (from romio) between an old saved test of 1.8.5rc3 on OpenBSD-5.6 and a fresh test of 1.8.6rc1 on OpenBSD-5.7: checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes -checking sys/mount.h usability... no +checking sys/mount.h usability... yes checking sys/mount.h presence... yes -configure: WARNING: sys/mount.h: present but cannot be compiled -configure: WARNING: sys/mount.h: check for missing prerequisite headers? -configure: WARNING: sys/mount.h: see the Autoconf documentation -configure: WARNING: sys/mount.h: section "Present But Cannot Be Compiled" -configure: WARNING: sys/mount.h: proceeding with the compiler's result -configure: WARNING: ## -------------------------------- ## -configure: WARNING: ## Report this to disc...@mpich.org ## -configure: WARNING: ## -------------------------------- ## -checking for sys/mount.h... no +checking for sys/mount.h... yes checking sys/statvfs.h usability... yes checking sys/statvfs.h presence... yes checking for sys/statvfs.h... yes -checking whether struct statfs properly defined... no +checking whether struct statfs properly defined... yes checking for f_fstypename member of statfs structure... yes checking for sys/stat.h... (cached) yes checking for sys/types.h... (cached) yes This suggests to me that code that may have been unreachable under OpenBSD 5.6 is now being built (unsuccessfully) under OpenBSD 5.7. Specifically the "struct statfs properly defined" test result has changed from "no" to "yes". To me it looks like the failing code assumes that if that configure test passed, then struct statfs contains a f_type field. I do notice that Open MPI's configure actually checks rather than assuming this: checking for struct statfs.f_type... no -Paul On Sun, May 24, 2015 at 5:57 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > I see a failure on OpenBSD when building ROMIO: > > libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio > -I./adio/include -DOMPI_BUILDING=1 > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/../../../../.. > -I/home/phargrov/OMPI/openmpi-1.8.6r > c1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/../../../../../opal/include > -I./../../../../../opal/include -I./../../../../../ompi/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc > 1/ompi/mca/io/romio/romio/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/include > -I./include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8. > 6rc1/ompi/mca/io/romio/romio/include -I./mpi-io > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi- > 1.8.6rc1/ompi/mca/io/romio/romio/mpi-io -I./adio/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64 > /openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/o > penmpi-1.8.6rc1/opal/mca/hwloc/hwloc191/hwloc/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/BL > D/opal/mca/hwloc/hwloc191/hwloc/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1 > /opal/mca/event/libevent2021/libevent > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/o > pal/mca/event/libevent2021/libevent/include > -I/home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/BLD/opal/mca > /event/libevent2021/libevent/include -g -finline-functions > -fno-strict-aliasing -pthread -DHAVE_ROMIOCONF_H -I > ./include -MT adio/common/ad_fstype.lo -MD -MP -MF > adio/common/.deps/ad_fstype.Tpo -c /home/phargrov/OMPI/open > mpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/common/ad_fstype.c > -fPIC -DPIC -o a > dio/common/.libs/ad_fstype.o > > /home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/common/ad_fs > type.c: In function 'ADIO_FileSysType_fncall': > /home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/common/ad_fstype.c:374: > error: 'struct statfs' has no member named 'f_type' > /home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/common/ad_fstype.c:398: > error: 'struct statfs' has no member named 'f_type' > /home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/openmpi-1.8.6rc1/ompi/mca/io/romio/romio/adio/common/ad_fstype.c:419: > error: 'struct statfs' has no member named 'f_type' > *** Error 1 in ompi/mca/io/romio/romio (Makefile:3335 > 'adio/common/ad_fstype.lo') > *** Error 1 in ompi/mca/io/romio/romio (Makefile:4196 'all-recursive') > *** Error 1 in ompi/mca/io/romio (Makefile:1840 'all-recursive') > *** Error 1 in ompi (Makefile:3164 'all-recursive') > *** Error 1 in /home/phargrov/OMPI/openmpi-1.8.6rc1-openbsd5-amd64/BLD > (Makefile:1724 'all-recursive') > > This was NOT present in my testing of 1.8.5rc3. > HOWEVER the host has been updated from OpenBSD-5.6 to 5.7. > So, I don't yet know if the problem is due to a change in OMPI or in the > host. > I will report again when I know more. > > -Paul > > On Sat, May 23, 2015 at 1:28 PM, Ralph Castain <r...@open-mpi.org> wrote: > >> Usual place: >> >> http://www.open-mpi.org/software/ompi/v1.8/ >> >> 1.8.6 >> ----- >> >> - Fixed memory leak on Mac OS-X exposed by TCP keepalive >> - Fixed keepalive support to ensure that daemon/node failure >> results in complete job cleanup >> - Update Java binding support >> - Fixed MPI_THREAD_MULTIPLE bug in vader shared memory BTL >> - Fixed issue during shutdown when CUDA initialization wasn't complete >> - Fixed orted environment when no prefix given >> - Fixed trivial typo in MPI_Neighbor_allgather manpage >> - Fixed tree-spawn support for sh and ksh shells >> - Several data type fixes >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2015/05/17447.php >> > > > > -- > Paul H. Hargrove phhargr...@lbl.gov > Computer Languages & Systems Software (CLaSS) Group > Computer Science Department Tel: +1-510-495-2352 > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > -- Paul H. Hargrove phhargr...@lbl.gov Computer Languages & Systems Software (CLaSS) Group Computer Science Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
