From: Francois <devel.fx.lebail@orange.fr>
To: dev@dpdk.org
Subject: Warnings in headers when building libpcap with dpdk and clang
Date: Thu, 14 Aug 2025 14:53:56 +0200 [thread overview]
Message-ID: <be3d5abb-84cd-44de-b7c3-286536f7f994@orange.fr> (raw)
Hello,
I notice many warnings. To reproduce:
On Debian bookworm.
sudo apt install dpdk-dev
git clone https://git.tcpdump.org/libpcap
# build with clang
$ ./autogen.sh
$ ./configure CC=clang-16 --with-dpdk
$ make
Warning lines:
/usr/include/dpdk/rte_ring_elem_pvt.h:13:36: warning: 'GCC_VERSION' is not defined, evaluates to 0 [-Wundef]
/usr/include/dpdk/rte_ring_generic_pvt.h:93:28: warning: possible misuse of comma operator here [-Wcomma]
/usr/include/dpdk/rte_ring_elem_pvt.h:391:36: warning: 'GCC_VERSION' is not defined, evaluates to 0 [-Wundef]
/usr/include/dpdk/../x86_64-linux-gnu/dpdk/rte_memcpy.h:25:36: warning: 'GCC_VERSION' is not defined, evaluates to 0 [-Wundef]
/usr/include/dpdk/../x86_64-linux-gnu/dpdk/rte_memcpy.h:873:36: warning: 'GCC_VERSION' is not defined, evaluates to 0 [-Wundef]
/usr/include/dpdk/rte_flow.h:176:6: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:674:5: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:2223:6: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:2235:6: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:2247:6: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:2656:6: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:2940:5: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:2962:5: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_flow.h:4218:5: warning: declaration is marked with '@deprecated' command but does not have a deprecation attribute [-Wdocumentation-deprecated-sync]
/usr/include/dpdk/rte_ethdev.h:3568:10: warning: unrecognized parameter passing direction, valid directions are '[in]', '[out]' and '[in,out]' [-Wdocumentation]
/usr/include/dpdk/rte_ethdev.h:5375:10: warning: unrecognized parameter passing direction, valid directions are '[in]', '[out]' and '[in,out]' [-Wdocumentation]
What do you think?
--
Francois
next reply other threads:[~2025-08-14 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 12:53 Francois [this message]
2025-08-14 13:28 ` Marat Khalili
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=be3d5abb-84cd-44de-b7c3-286536f7f994@orange.fr \
--to=devel.fx.lebail@orange.fr \
--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).