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 favor of --with-verbs)
On Jan 8, 2014, at 8:38 PM, Paul Hargrove <phhargrove_at_[hidden]> wrote:
> 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 compiler vendor... (cached) sun
> checking if want to add padding to the openib BTL control header... no
> checking for fcntl.h... (cached) yes
> checking for sys/poll.h... (cached) yes
> checking infiniband/verbs.h usability... yes
> checking infiniband/verbs.h presence... yes
> checking for infiniband/verbs.h... yes
> looking for library without search path
> checking for ibv_open_device in -libverbs... no
> checking if ConnectX XRC support is enabled... no
> checking if dynamic SL is enabled... no
> configure: WARNING: Verbs support requested (via --with-verbs) but not found.
> configure: WARNING: If you are using libibverbs v1.0 (i.e., OFED v1.0 or v1.1), you *MUST* have both the libsysfs headers and libraries installed. Later versions of libibverbs do not require libsysfs.
> configure: error: Aborting.
> This is despite an earlier:
> checking if MCA component btl:openib can compile... yes
> The error above is with the Solaris Studio compilers, but the same happens with the GNU compilers.
> The (compressed) full configure output for the GNU case is attached.
> This is a regression relative to the current 1.7.4rc, in which the openib btl works fine on Solaris-11/x86-64, by which I mean I can configure with --enable-openib and the following command line works:
> mpirun -host pcp-j-19,pcp-j-20 -mca btl openib,self -np 2 examples/ring_c
> My best guess is that either the libsysfs requirement itself OR its associated test is Linux-specific.
> Paul H. Hargrove PHHargrove_at_[hidden]
> Future Technologies Group
> Computer and Data Sciences Department Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> devel mailing list
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/