From: David Marchand <david.marchand@redhat.com>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: users <users@dpdk.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [dpdk-stable-24.11.3] bbdev_trace.h: No such file or directory
Date: Tue, 23 Sep 2025 09:14:24 +0200 [thread overview]
Message-ID: <CAJFAV8xh18gJtJF-Jy7feCk056PEsc1TZ9FGUU4XHKerKOMbZw@mail.gmail.com> (raw)
In-Reply-To: <CAJK_iehr+dfSM4BWj05+kmhav52__HjyzK=3ZFvXgykZfMHJoA@mail.gmail.com>
Hello,
On Mon, 22 Sept 2025 at 18:45, David Aldrich
<david.aldrich.ntml@gmail.com> wrote:
> I am upgrading our DPDK-enabled app from dpdk-stable-23.11.1 to
> dpdk-stable-24.11.3. With dpdk-stable-24.11.3 I get compilation error:
>
> In file included from <snip>:
> /opt/dpdk/dpdk-stable-24.11.3/install/include/rte_bbdev.h:36:10: fatal
> error: bbdev_trace.h: No such file or directory
Something is strange.
I see no reference to bbdev_trace.h in neither v24.11.3 tarball, nor
the 24.11 stable branch.
$ git grep bbdev_trace.h v24.11.3
It looks like you have some change in your dpdk copy, or I am missing
context to understand your report.
> We use pkg-config to provide cflags:
>
> $ pkg-config --cflags libdpdk
> -I/opt/dpdk/dpdk-stable-24.11.3/install/include -include rte_config.h
> -march=native -mrtm
>
> but the path to bbdev_trace.h is not included:
>
> $ find /opt/dpdk/dpdk-stable-24.11.3/ -name bbdev_trace.h
> /opt/dpdk/dpdk-stable-24.11.3/lib/bbdev/bbdev_trace.h
Which is expected.
bbdev_trace.h is a private header that is not exported.
--
David Marchand
next prev parent reply other threads:[~2025-09-23 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 16:44 David Aldrich
2025-09-23 7:14 ` David Marchand [this message]
2025-09-23 16:04 ` David Aldrich
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=CAJFAV8xh18gJtJF-Jy7feCk056PEsc1TZ9FGUU4XHKerKOMbZw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=david.aldrich.ntml@gmail.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=users@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).