From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 910] [build] meson build not support some c_args
Date: Wed, 15 Dec 2021 08:18:20 +0000 [thread overview]
Message-ID: <bug-910-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=910
Bug ID: 910
Summary: [build] meson build not support some c_args
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: junx.dong@intel.com
Target Milestone: ---
1.DPDK version:
version: 21.11.0-rc0
2.OS version:
OS: Ubuntu 20.04.3 LTS/5.8.0-48-generic
gcc version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
3. Config meson build command, contain c_args parameter
DRTE_MBUF_DEFAULT_MEMPOOL_OPS, as follow:
CC=gcc meson -Denable_kmods=True -Dlibdir=lib -Dc_args=-DRTE_MBUF_DEFAULT_
MEMPOOL_OPS=stack --default-library=static x86 _64-native-linuxapp-gcc
4. Check the build output.
There is warning information of redefined parameter
171149 [6/2720] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_
hypervisor.c.o^M
171150 In file included from <command-line>:^M ./config/rte_config.h:52:
warning:
"RTE_MBUF_DEFAULT_MEMPOOL_OPS" redefined^M #define
RTE_MBUF_DEFAULT_MEMPOOL_OPS
"ring_mp_mc"^M
5. The list of othe c_args parameters having same issues:
RTE_LIBRTE_IP_FRAG_MAX_FRAG
RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM
RTE_LIBRTE_I40E_RX_ALLOW_BULK_ALLOC
6. About RTE_LIBRTE_I40E_16BYTE_RX_DESC, it was undefined in
config/rte_config.h,
if i defined it in meson build command, it is also cancel, please also
analysis
this parameter. thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-12-15 8:18 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-910-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).