DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marat Khalili <marat.khalili@huawei.com>
To: Francois <devel.fx.lebail@orange.fr>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Warnings in headers when building libpcap with dpdk and clang
Date: Thu, 14 Aug 2025 13:28:04 +0000	[thread overview]
Message-ID: <145abf7b6da64c229fc99ab580973eb5@huawei.com> (raw)
In-Reply-To: <be3d5abb-84cd-44de-b7c3-286536f7f994@orange.fr>

> -----Original Message-----
> From: Francois <devel.fx.lebail@orange.fr>
> Sent: Thursday 14 August 2025 13:54
> To: dev@dpdk.org
> Subject: Warnings in headers when building libpcap with dpdk and clang
> 
> 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]

> What do you think?

For the first warning there was a commit 3cb34fb0b0 "build: set toolchain macros from predefined macros" dated 2024-01-02 that was fixing similar issue. It is possible that documentation issues were fixed since bookworm-shipped version 22.11 as well. Depending on your goals you may try newer DPDK version, compiling libpcap with gcc and/or fewer warnings or just ignoring these warnings.

      reply	other threads:[~2025-08-14 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 12:53 Francois
2025-08-14 13:28 ` Marat Khalili [this message]

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=145abf7b6da64c229fc99ab580973eb5@huawei.com \
    --to=marat.khalili@huawei.com \
    --cc=dev@dpdk.org \
    --cc=devel.fx.lebail@orange.fr \
    /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).