From: Thomas Monjalon <thomas@monjalon.net>
To: Vineeth Thapeta <vthape2@uic.edu>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Trouble Building DPDK with MLNX OFED(4.4) Works with 5.0
Date: Sat, 06 Jun 2020 22:13:09 +0200 [thread overview]
Message-ID: <4178299.QiJXgQhXax@thomas> (raw)
In-Reply-To: <CADWAvF6J5_+UdOywE5JQSaoh6AcXJeoB88byFkb466_KvybvUQ@mail.gmail.com>
Hi,
06/06/2020 21:43, Vineeth Thapeta:
> Hi guys,
>
> I had to roll back OFED version from 5.0 to 4.4 because another library
> Moongen has trouble building with OFED 5.0.
How Moongen is related to OFED?
Why using OFED and not upstream packaging of rdma-core?
Which distribution are you using?
> I rolled back the version and
> Moongen builds and when I try to build dpdk 18.11, 19.11,17.11. All the
> three builds fail with the following error (https://pastebin.com/fiw7iz1Z
> Link of build error). Does anyone know why this happens.
Any DPDK version should build with any version of OFED or rdma-core.
Note: DPDK 17.11 is not supported anymore.
> I am exhausted
> with roll backs,if anyone can help me with this I would be grateful. , By
> the looks of it, it might mean it had problems with the OFED driver? I
> installed the MLNX ofed driver without any flags, i.e ./mlnxofedinstall. If
> you want any further information,please let me know. Any suggestion would
> be appreciated, even if you don't think it might work. I have been trying
> to install these two for the past week, without much success. Are the above
> mentioned DPDK version not compatible with said driver(4.4)?
Let's focus on your goal and see what is the real issue you hit.
Which version of DPDK do you need?
Why not start with the latest LTS, which is 19.11?
next prev parent reply other threads:[~2020-06-06 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 19:43 Vineeth Thapeta
2020-06-06 20:13 ` Thomas Monjalon [this message]
2020-06-06 20:54 ` Vineeth Thapeta
2020-06-06 21:55 ` Thomas Monjalon
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=4178299.QiJXgQhXax@thomas \
--to=thomas@monjalon.net \
--cc=users@dpdk.org \
--cc=vthape2@uic.edu \
/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;
as well as URLs for NNTP newsgroup(s).