HI Ralph,

Jeff fixed this in c40fd09.  That's the problem I hit, in addition to
later not having psm_infinipath.  After that commit,and commit cd0a54d
you should be able to config and make again.

Howard






2014-12-09 13:45 GMT-08:00 Ralph Castain <r...@open-mpi.org>:

> Just as an FYI: we discovered that libfabric requires libnl, and that the
> configure logic doesn’t kick you out if libnl isn’t found - you just fail
> during compile.
>
>
> > On Dec 9, 2014, at 6:29 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>
> wrote:
> >
> > As I mentioned on the call a week ago, the usnic BTL has been updated to
> use libfabric (instead of verbs).
> >
> > What is libfabric?
> > --> Think of it as a "next generation verbs" -- it's OS-bypass
> networking for a wide range of network hardware, and libfabric contains
> many more capabilities than the verbs API.  libfabric is being developed by
> most the same people who initially developed verbs; it's not in competition
> with verbs -- it's a true "next generation" effort.  See
> http://ofiwg.github.io/libfabric/ for more detail.
> >
> > Why should anyone care?
> > --> The usnic BTL has been updated to use libfabric.  I have therefore
> removed all usnic-specific code from the verbs parts of the OMPI code base
> (e.g., opal/mca/common).  Additionally, there will shortly be another
> commit that introduces another OMPI network device that uses libfabric.
> >
> > Did you really just embed libfabric in opal/common/libfabric?
> > --> Yes -- but this is temporary.  libfabric isn't v1.0 yet -- there
> aren't libfabric tarballs being distributed.  Hence, other than git-cloning
> the libfabric github repo, you can't easily build OMPI against libfabric.
> So we are temporarily embedding a copy of libfabric in OMPI, partly for
> convenience, and partly because the libfabric API is still changing
> slightly -- we need a stable libfabric stake in the ground against which to
> build the usnic and other components.  We'll update the embedded libfabric
> periodically to keep up with its development (e.g., I just did, earlier
> this morning).  We anticipate removing the embedded copy of libfabric at
> some point in the future.
> >
> > Whoa; I'm getting a slew of -pedantic warnings when compiling libfabric!
> > --> Yeah, sorry about that.  :-(  I added a pragma this morning that
> should remove some of them, but there's still a bunch of -pedantic warnings
> when you compile opal/mca/common/libfabric.  We're working with libfabric
> upstream to get them fixed.  Stay tuned.
> >
> > --
> > 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
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/12/16468.php
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/12/16480.php

Reply via email to