All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1814] dmadev build fails if debug enabled
Date: Mon, 27 Oct 2025 16:32:20 +0000	[thread overview]
Message-ID: <bug-1814-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1814

            Bug ID: 1814
           Summary: dmadev build fails if debug enabled
           Product: DPDK
           Version: 25.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

I do test build with all the XXX_DEBUG options enabled.
If RTE_DMADEV_DEBUG is enabled, then build fails here:

FAILED: lib/librte_dmadev.a.p/dmadev_rte_dmadev_trace_points.c.o 
cc -Ilib/librte_dmadev.a.p -Ilib -I../lib -Ilib/dmadev -I../lib/dmadev
-Ilib/eal/common -I../lib/eal/common -I. -I.. -Iconfig -I../config
-Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include
-I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include
-I../kernel/linux -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log
-I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry
-Ilib/argparse -I../lib/argparse -I/usr/include/x86_64-linux-gnu
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra
-std=c11 -O3 -include rte_config.h -Wvla -Wcast-qual -Wdeprecated -Wformat
-Wformat-nonliteral -Wformat-security -Wmissing-declarations
-Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith
-Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings
-Wno-packed-not-aligned -Wno-missing-field-initializers
-fzero-init-padding-bits=all -D_GNU_SOURCE -DRTE_ENABLE_ASSERT
-DRTE_LIBRTE_ETHDEV_DEBUG=1 -DRTE_LIBRTE_IPFRAG_TBL_STAT
-DRTE_LIBRTE_MEMPOOL_STATS -DRTE_LIBRTE_MEMPOOL_DEBUG -DRTE_DMADEV_DEBUG
-DRTE_EVENTDEV_DEBUG -DRTE_POWER_DEBUG -DRTE_TIMER_DEBUG -DRTE_VHOST_DEBUG
-DRTE_SCHED_DEBUG -DRTE_SORING_DEBUG -DRTE_MALLOC_DEBUG -DRTE_MBUF_DEBUG
-DRTE_MBUF_HISTORY_DEBUG -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API
-DALLOW_INTERNAL_API -Wno-format-truncation
-DRTE_LOG_DEFAULT_LOGTYPE=lib.dmadev -MD -MQ
lib/librte_dmadev.a.p/dmadev_rte_dmadev_trace_points.c.o -MF
lib/librte_dmadev.a.p/dmadev_rte_dmadev_trace_points.c.o.d -o
lib/librte_dmadev.a.p/dmadev_rte_dmadev_trace_points.c.o -c
../lib/dmadev/rte_dmadev_trace_points.c
In file included from ../lib/dmadev/rte_dmadev_trace.h:16,
                 from ../lib/dmadev/rte_dmadev_trace_points.c:8:
../lib/dmadev/rte_dmadev.h: In function ‘rte_dma_copy’:
../lib/dmadev/rte_dmadev.h:1183:25: error: ‘EINVAL’ undeclared (first use in
this function)
 1183 |                 return -EINVAL;
      |                         ^~~~~~
../lib/dmadev/rte_dmadev.h:1183:25: note: each undeclared identifier is
reported only once for each function it appears in
../lib/dmadev/rte_dmadev.h:1185:25: error: ‘ENOTSUP’ undeclared (first use in
this function)
 1185 |                 return -ENOTSUP;
      |                         ^~~~~~~
../lib/dmadev/rte_dmadev.h: In function ‘rte_dma_copy_sg’:
../lib/dmadev/rte_dmadev.h:1235:25: error: ‘EINVAL’ undeclared (first use in
this function)
 1235 |                 return -EINVAL;
      |                         ^~~~~~
../lib/dmadev/rte_dmadev.h:1237:25: error: ‘ENOTSUP’ undeclared (first use in
this function)
 1237 |                 return -ENOTSUP;
      |                         ^~~~~~~
../lib/dmadev/rte_dmadev.h: In function ‘rte_dma_fill’:
../lib/dmadev/rte_dmadev.h:1282:25: error: ‘EINVAL’ undeclared (first use in
this function)
 1282 |                 return -EINVAL;
      |                         ^~~~~~
../lib/dmadev/rte_dmadev.h:1284:25: error: ‘ENOTSUP’ undeclared (first use in
this function)
 1284 |                 return -ENOTSUP;
      |                         ^~~~~~~
../lib/dmadev/rte_dmadev.h: In function ‘rte_dma_submit’:
../lib/dmadev/rte_dmadev.h:1315:25: error: ‘EINVAL’ undeclared (first use in
this function)
 1315 |                 return -EINVAL;
      |                         ^~~~~~
../lib/dmadev/rte_dmadev.h:1317:25: error: ‘ENOTSUP’ undeclared (first use in
this function)
 1317 |                 return -ENOTSUP;
      |                         ^~~~~~~
ninja: build stopped: subcommand failed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2025-10-27 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 16:32 bugzilla [this message]
2025-11-04 10:45 ` [DPDK/other Bug 1814] dmadev build fails if debug enabled bugzilla

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-1814-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.