From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Jason Gunthorpe'
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH rdma-core] Add -DIN_PLACE=1 to cmake
Date: Thu, 22 Dec 2016 16:30:17 -0600 [thread overview]
Message-ID: <029801d25ca2$f8bb2f80$ea318e80$@opengridcomputing.com> (raw)
In-Reply-To: <20161222221559.GA15947-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
> This configures the paths to run the software from the local build
> directory. Much of this is done automatically by how cmake uses rpath,
> but the two cases where we dlopen things have to be handled by us.
>
> The simple solution is to hard wire the build directory path into the
> binaries.
>
> 'etc' is also relocated to build/etc/ as that is part of how the verbs
> providers are located.
>
> Signed-off-by: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
> ---
> CMakeLists.txt | 23 +++++++++++++++++++++--
> README.md | 3 ++-
> build.sh | 4 ++--
> buildlib/rdma_functions.cmake | 4 ++--
> ibacm/CMakeLists.txt | 5 +++++
> 5 files changed, 32 insertions(+), 7 deletions(-)
>
> Steve, this is a refined version of what I sent you ealier, does it
> work for you?
>
I was able to run rping from build/bin/rping and it loaded
build/lib/libcxgb4-rdmav2.so, so it worked for me.
Tested-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
--
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-12-22 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 22:15 [PATCH rdma-core] Add -DIN_PLACE=1 to cmake Jason Gunthorpe
[not found] ` <20161222221559.GA15947-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-12-22 22:30 ` Steve Wise [this message]
2016-12-23 12:12 ` Doug Ledford
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='029801d25ca2$f8bb2f80$ea318e80$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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