With many testers still running at this time, the first to complete is a failure report.
>From a FreBSD-6/amd64 platform: CCLD otfmerge-mpi /data/home/hargrove/OMPI/openmpi-1.7.5rc1-freebsd6-amd64/BLD/ompi/contrib/vt/vt/../../../.libs/libmpi.a(osc_sm _passive_target.o)(.text+0x18b): In function `lk_fetch32': /data/home/hargrove/OMPI/openmpi-1.7.5rc1-freebsd6-amd64/openmpi-1.7.5rc1/ompi/mca/osc/sm/:51: undefined reference to `__sync_synchronize' Keep in mind that with 99% certainty this has NOTHING to do with VT. It just happens thatotfmerge-mpi is the first executable linked with libmpi. Rather the fault lies with the __sync_synchronize call in osc_sm_passive_target.c. The __sync_synchronize() call is not only gcc-specific, but didn't exist prior to about gcc-4.1. Surely there must be a opal call that should be used here instead? There is no reason to think this is specific to FreeBSD-6, but rather the use of a gcc older than the addition of __sync_syncronize() seems the most likely key to exposing the problem. I suspect that as my non-gcc testers complete (esp. PGI and Sun) this same issue will arise there. On Sat, Mar 1, 2014 at 6:13 PM, Ralph Castain <[email protected]> wrote: > In the usual place: > > http://www.open-mpi.org/software/ompi/v1.7/ > > Please subject this to your best tests as we hope to roll this (plus bug > fixes) to 1.8.0 at the end of the month. This includes the new OSHMEM > support, plus a completely updated MPI-3 compliant one-sided implementation. > > Scheduled release date: Mar 10 > > Thanks > Ralph > > _______________________________________________ > devel mailing list > [email protected] > http://www.open-mpi.org/mailman/listinfo.cgi/devel > -- Paul H. Hargrove [email protected] Future Technologies Group Computer and Data Sciences Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
