From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "ira.weiny" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rdma-core make install failing
Date: Thu, 23 Feb 2017 16:12:47 -0700 [thread overview]
Message-ID: <20170223231247.GB18086@obsidianresearch.com> (raw)
In-Reply-To: <20170223230008.GA546-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
On Thu, Feb 23, 2017 at 06:00:09PM -0500, ira.weiny wrote:
> I'm not sure what I'm doing wrong but make install seems to be deleting a
> library and then complaining that it can't find it for installation... :-/
>
> After running build.sh I ran make install and get this error:
Oh.. you can't 'make install' when using build.sh. I guess we should
have a more explicit error message for this case.
build.sh now uses -DIN_PLACE=1 which arranges for everything to run
smoothly without being installed. Just run build/bin/blat or do
LD_LIBRARY_PATH=`pwd`/build/bin to use the new library with something
out of tree. There is no longer a big reason for developers to 'make
install' anymore.
Part of the trick that happens to make IN_PLACE work is that the
install path is set to /nfs/site/home/iweiny/rdma-core/build/lib/
which means 'make install' tries to overwrite the built output and
just generally makes a mess.
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:[~2017-02-23 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 23:00 rdma-core make install failing ira.weiny
[not found] ` <20170223230008.GA546-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2017-02-23 23:12 ` Jason Gunthorpe [this message]
[not found] ` <20170223231247.GB18086-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-24 2:41 ` Weiny, Ira
[not found] ` <2807E5FD2F6FDA4886F6618EAC48510E3C6513E7-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-02-24 18:25 ` Jason Gunthorpe
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=20170223231247.GB18086@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@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