From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 416] nfb build failed - missing rpms?
Date: Tue, 03 Mar 2020 19:05:48 +0000 [thread overview]
Message-ID: <bug-416-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=416
Bug ID: 416
Summary: nfb build failed - missing rpms?
Product: DPDK
Version: 20.02
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: kevuzaj@gmail.com
Target Milestone: ---
Looks like either correct rpms are missing, or there is an issue building with
meson (or I missed some step).
Docs [1] say to use
* for DPDK from 19.05
on the linked site, there is no files referencing v19.05
https://www.netcope.com/en/company/community-support/dpdk-libsze2#NFB
Latest files that seem relevant as they are **from** 18.05
- DPDK from 18.05
Downloaded those rpms, installed on Fedora 31:
# rpm -qa | grep netcope
netcope-common-light-4.4.1-1.x86_64
netcope-common-dpdk-4.4.1-1.x86_64
# cat /etc/redhat-release
Fedora release 31 (Thirty One)
# uname -a
Linux wsfd-netdev14.ntdv.lab.eng.bos.redhat.com 5.5.7-200.fc31.x86_64 #1 SMP
Fri Feb 28 17:18:37 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
did not change config in config/common_base
meson sees that deps are available:
net:
af_packet, af_xdp, ark, atlantic, avp, axgbe, bond, bnx2x,
bnxt, cxgbe, dpaa, dpaa2, e1000, ena, enetc, enic,
failsafe, fm10k, i40e, hinic, hns3, iavf, ice, ifc,
ixgbe, kni, liquidio, memif, mlx4, mlx5, netvsc, ***nfb***,
compilation fails:
In file included from ../drivers/net/nfb/nfb_rx.c:9:
../drivers/net/nfb/nfb_rx.h:10:10: fatal error: nfb/nfb.h: No such file or
directory
10 | #include <nfb/nfb.h>
| ^~~~~~~~~~~
[1] http://git.dpdk.org/dpdk/tree/doc/guides/nics/nfb.rst#n60
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-03-03 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-416-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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.