From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 356] Building dpdk with rte_vhost sometimes fails due to missing rte_hash.h
Date: Wed, 23 Oct 2019 10:48:35 +0000 [thread overview]
Message-ID: <bug-356-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=356
Bug ID: 356
Summary: Building dpdk with rte_vhost sometimes fails due to
missing rte_hash.h
Product: DPDK
Version: 19.05
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: jan.kryl@mayadata.io
Target Milestone: ---
This is because rte_vhost does not name rte_hash as its dependency in
lib/Makefile. Depending on -j and how knows what else the build either succeeds
or fails and is nondeterministic.
> == Build lib/librte_vhost
> SYMLINK-FILE include/rte_vhost.h
> SYMLINK-FILE include/rte_vdpa.h
> SYMLINK-FILE include/rte_vhost_crypto.h
> CC fd_man.o
> CC iotlb.o
> CC socket.o
> CC vhost.o
> CC vhost_user.o
> CC virtio_net.o
> CC vdpa.o
> CC vhost_crypto.o
>
> /tmp/nix-build-libspdk.drv-0/source/dpdk/lib/librte_vhost/vhost_crypto.c:5:10:
> > fatal error: rte_hash.h: No such file or directory
> #include <rte_hash.h>
> ^~~~~~~~~~~~
> compilation terminated.
The fix is simple. DEPDIRS for librte_vhost in lib/Makefile needs to explicitly
mention librte_hash:
> DEPDIRS-librte_vhost := librte_eal librte_mempool librte_mbuf librte_ethdev \
> librte_net librte_hash
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-10-23 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:48 bugzilla [this message]
2019-11-21 2:02 ` [dpdk-dev] [Bug 356] Building dpdk with rte_vhost sometimes fails due to missing rte_hash.h bugzilla
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-356-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.