From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdma-core, cmake/ninja question
Date: Thu, 22 Sep 2016 13:29:32 -0600 [thread overview]
Message-ID: <20160922192932.GA25659@obsidianresearch.com> (raw)
In-Reply-To: <019201d21501$3a191a80$ae4b4f80$@opengridcomputing.com>
On Thu, Sep 22, 2016 at 01:43:36PM -0500, Steve Wise wrote:
> > Apply this patch:
> >
> > https://github.com/jgunthorpe/rdma-
> > plumbing/commit/64ed4fd30a2157bdaf0a8f7f1b04d2dad02c1b8f
> >
> > It hardwires the search path into libverbs and libverbs will look into
> > the place it was installed before searching the system library
> > path. That will eliminate the problem you mentioned above.
> >
> > Further, after that patch is applied you can do a rough imitation of
> > 'run-in-place' like this:
> >
> > $ cmake .. -DVERBS_PROVIDER_DIR:PATH=`pwd`/lib -
> > DSYSCONF_INSTALL_DIR:PATH=/etc
> >
>
> And how do I build this after the cmake?
Sorry, you always need the -GNinja, I was just being brief
I also mistyped the ETC name.
I tested this:
$ mkdir build ; cd build
$ cmake .. -GNinja -DVERBS_PROVIDER_DIR:PATH=`pwd`/lib -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc
$ ninja
$ strace bin/ibv_devinfo 2>&1 | grep -i rdmav2
open("/tmp/rdma-core/build/lib/libmlx4-rdmav2.so", O_RDONLY|O_CLOEXEC) = 3
Note LD_LIBRARY_PATH is needed to run things from outside build/bin/
I have some thoughts to make this simpler, call it a proof of concept for
run-from-build ..
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-22 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 15:35 rdma-core, cmake/ninja question Steve Wise
2016-09-22 15:48 ` Jason Gunthorpe
[not found] ` <20160922154814.GB15212-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-22 16:21 ` Steve Wise
2016-09-22 16:31 ` Jason Gunthorpe
[not found] ` <20160922163143.GC6994-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-22 18:43 ` Steve Wise
2016-09-22 19:29 ` Jason Gunthorpe [this message]
[not found] ` <20160922192932.GA25659-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-22 19:34 ` Steve Wise
2016-09-22 19:38 ` Jason Gunthorpe
[not found] ` <014601d214ed$6e4a8d70$4adfa850$@opengridcomputing.com>
2016-09-22 16:23 ` Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160922192932.GA25659@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox