We have a subtle bug with the atomic selection. On Linux the CMA support is linked together with the OPAL_ASSEMBLY_ARCH. If the BUILTIN atomics are enabled, and we are on Linux and we need to define the CMA syscall# (OMPI_BTL_SM_CMA_NEED_SYSCALL_DEFS), the opal/include/opal/sys/cma.h file is unable to make a decision as the underlying architecture is unknown (BUILTIN not being a valid architecture).
I think the solution is to have two versions of OPAL_ASSEMBLY_ARCH, one for knowing the architecture (excluding OMPI_SYNC_BUILTIN) and one for selecting the atomics (oncluding OMPI_SYNC_BUILTIN) we want to use. Fixing this however involves too much .m4 craftsmanship for my liking, so a volunteer will be needed
Once fixed this should go into 1.7 together with 29915, 29916.
On Dec 12, 2013, at 13:31 , Philipp Thomas <pth_at_[hidden]> wrote:
> * Jeff Squyres (jsquyres) (jsquyres_at_[hidden]) [20131211 21:01]:
>> Can you send the opal_config.h file from your build tree?
>> This will help us look into what's going on.
> Note that it doesn't seem to be dependent on the build architecture as it
> fails at the same spot for all Archs that openSUSE supports (i586, x86-64,
> armv6l, armv7l ppc, ppc64).
> devel mailing list