From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 387] Disabling octeontx in meson leads to meson configure failure
Date: Thu, 30 Jan 2020 16:51:08 +0000 [thread overview]
Message-ID: <bug-387-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=387
Bug ID: 387
Summary: Disabling octeontx in meson leads to meson configure
failure
Product: DPDK
Version: 20.02
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: anatoly.burakov@intel.com
Target Milestone: ---
When running meson configure with disabled octeontx drivers, the configure step
fails.
Configure command to reproduce:
meson build/
-Ddisable_drivers=common/octeontx,common/octeontx2,net/octeontx,net/octeontx2,mempool/octeontx,mempool/octeontx2
Error output:
<...>
drivers/net/octeontx/base/meson.build:13:1: ERROR: Tried to get unknown
variable "static_rte_mempool_octeontx".
<...>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-01-30 16:51 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-387-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 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).