To tie up this thread: I investigated and found the issue.
I started a new thread because it's going to take some discussion to figure out
the right way to fix this
(http://www.open-mpi.org/community/lists/devel/2014/01/13744.php).
On Jan 10, 2014, at 10:24 PM, Paul Hargrove wrote:
> FYI: st
FYI: still present in tonight's trunk tarball (1.9a1r30255).
Don't know if was expected to be fixed or not.
-Paul
On Thu, Jan 9, 2014 at 2:24 PM, Paul Hargrove wrote:
> Jeff,
>
> The requested config.log was attached
> as openmpi-trunk-solaris11-x64-ib-gcc452-config.log.bz2 in my recent
> resp
Jeff,
The requested config.log was attached
as openmpi-trunk-solaris11-x64-ib-gcc452-config.log.bz2 in my recent
response to the usnic-on-solaris thread:
http://www.open-mpi.org/community/lists/devel/2014/01/13637.php
It looks like there were 2 successful probes for ibv_open_device() before
the f
Paul --
Can you send the config.log file from this? It has more details in it that
will be useful (e.g., *why* ibv_open_device wasn't found in -libverbs).
I wonder if the issue has to do something with our handling of the legacy
--with-openib switch...? (it's been deprecated on the trunk in fa
When trying to configure the OMPI trunk on a Solaris-11/x86-64 with
--enable-openib, I see the following error not seen with the 1.7 branch:
*** Compiler flags
checking which of CFLAGS are ok for debugger modules... -DNDEBUG -m64 -mt
checking for debugger extra CFLAGS... -g
checking for the C com