From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: oulijun <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Linuxarm <linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [bug] build the user-space stack code in github is fail on ubuntu
Date: Fri, 14 Oct 2016 10:46:04 -0600 [thread overview]
Message-ID: <20161014164604.GC6258@obsidianresearch.com> (raw)
In-Reply-To: <5800A467.2020602-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Fri, Oct 14, 2016 at 05:24:55PM +0800, oulijun wrote:
> ubuntu@62fe1357a077:~/rdma_core/rdma-core/build_1$ cmake ..
> CMake Error at CMakeLists.txt:199 (message):
> Cannot find libnl-3.0 or libnl-1
There are directions in README.md you need to follow:
$ apt-get install build-essential cmake gcc libnl-3-dev libnl-route-3-dev ninja-build pkg-config valgrind
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-10-14 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 9:24 [bug] build the user-space stack code in github is fail on ubuntu oulijun
[not found] ` <5800A467.2020602-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-14 9:41 ` oulijun
[not found] ` <5800A835.5020207-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-10-14 11:56 ` Leon Romanovsky
2016-10-14 16:48 ` Jason Gunthorpe
2016-10-14 16:46 ` Jason Gunthorpe [this message]
[not found] ` <20161014164604.GC6258-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-17 8:48 ` oulijun
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=20161014164604.GC6258@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=oulijun-hv44wF8Li93QT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.