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 <phhargr...@lbl.gov> wrote:

> 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 <phhargr...@lbl.gov> wrote:
> 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 
> failing one.
> The failing one says:
> configure:284324: checking for ibv_open_device in -libverbs
> configure:284349: gcc -std=gnu99 -o conftest -O3 -DNDEBUG -m64 
> -finline-functions -fno-strict-aliasing -pthread -I$(top_srcdir) 
> -I$(top_builddir) -I$(top_srcdir)/opal/include -I$(top_srcdir)/orte/include 
> -I$(top_srcdir)/ompi/include -I$(top_srcdir)/oshmem/include    
> -I/shared/OMPI/openmpi-trunk-solaris11-x64-ib-gcc452/openmpi-1.9a1r30146/opal/mca/hwloc/hwloc172/hwloc/include
>  
> -I/shared/OMPI/openmpi-trunk-solaris11-x64-ib-gcc452/BLD/opal/mca/hwloc/hwloc172/hwloc/include
>  
> -I/shared/OMPI/openmpi-trunk-solaris11-x64-ib-gcc452/openmpi-1.9a1r30146/opal/mca/event/libevent2021/libevent
>  
> -I/shared/OMPI/openmpi-trunk-solaris11-x64-ib-gcc452/openmpi-1.9a1r30146/opal/mca/event/libevent2021/libevent/include
>  
> -I/shared/OMPI/openmpi-trunk-solaris11-x64-ib-gcc452/BLD/opal/mca/event/libevent2021/libevent/include
>  -export-dynamic    conftest.c -libverbs   -lsocket -lnsl  -lm  -lsocket 
> -lnsl  -lm  >&5
> ld: fatal: entry point symbol 'xport-dynamic' is undefined
> collect2: ld returned 1 exit status
> configure:284349: $? = 1
> 
> So, it looks line a bogus "-export-dynamic" argument to gcc is at fault here.
> 
> -Paul
> 
> 
> On Thu, Jan 9, 2014 at 2:05 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> 
> wrote:
> 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 favor of 
> --with-verbs)
> 
> 
> On Jan 8, 2014, at 8:38 PM, Paul Hargrove <phhargr...@lbl.gov> 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
> >
> > --
> > Paul H. Hargrove                          phhargr...@lbl.gov
> > Future Technologies Group
> > Computer and Data Sciences Department     Tel: +1-510-495-2352
> > Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
> > <configure.log.bz2>_______________________________________________
> > devel mailing list
> > de...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
> 
> 
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> 
> 
> 
> -- 
> Paul H. Hargrove                          phhargr...@lbl.gov
> Future Technologies Group
> Computer and Data Sciences Department     Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
> 
> 
> 
> -- 
> Paul H. Hargrove                          phhargr...@lbl.gov
> 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
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Reply via email to