From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "'Amrani, Ram'" <Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: Issues Building krping on RHEL 7.2
Date: Mon, 6 Mar 2017 08:51:05 -0600 [thread overview]
Message-ID: <084301d29689$15355b70$3fa01250$@opengridcomputing.com> (raw)
In-Reply-To: <DM3PR07MB22010C36EE6B652B1AA1356FF82D0-jBX7zO+Db/wI9Q/2ysJlLeFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
>
> Hi Steve,
> Are you the maintainer of krping?
> I've tried to build krping from
> https://github.com/larrystevenwise/krping.git.
> But I get multiple errors.
> I guess I'm missing something simple.
>
> i.e. -
> 0. RHEL 7.2 with INBOX OFED (tried also newer kernels)
> 1. git clone https://github.com/larrystevenwise/krping.git
> 2. vim Makefile and have 'KSRC=/usr/src/kernels/3.10.0-327.el7.x86_64/'
> 3. Make
>
> And I get all the errors below.
>
> Any clue?
Hey Ram. The krping code is only maintained on the most recent upstream
kernels. So your best shot is using >= 4.8. A quick compile on 4.10 works
for me.
Steve.
--
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-03-06 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 17:53 Issues Building krping on RHEL 7.2 Amrani, Ram
[not found] ` <DM3PR07MB22010C36EE6B652B1AA1356FF82D0-jBX7zO+Db/wI9Q/2ysJlLeFPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-03-06 14:51 ` Steve Wise [this message]
2017-03-08 10:03 ` Amrani, Ram
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='084301d29689$15355b70$3fa01250$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=Ram.Amrani-YGCgFSpz5w/QT0dZR+AlfA@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 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.