DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/cryptodev Bug 2050] ninja compile failure for arm
Date: Wed, 07 Oct 2026 20:38:29 +0000	[thread overview]
Message-ID: <bug-2050-3@https.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=2050

            Bug ID: 2050
           Summary: ninja compile failure for arm
           Product: DPDK
           Version: 26.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: abailey@iol.unh.edu
  Target Milestone: ---

Compiling dpdk on dpdk-next-crypto main branch yields a compile error on arm
systems. I believe This is due to the supported version of ipsec mb library in
DPDK being v2.0.0 while the latest version available on arm is 1.5.0. The arm
fork of ipsec mb can be found here: 
  * https://gitlab.arm.com/arm-reference-solutions/ipsec-mb/-/tree/main/

The build commands to produce this error are:

"meson setup --default-library=static -Dlibdir=lib /tmp/dts.9zK3U/dpdk
/tmp/dts.9zK3U/dpdk/aarch64-linux-gcc"

"ninja -C /tmp/dts.9zK3U/dpdk/aarch64-linux-gcc"

Yields error:

[2747/3503] Compiling C object
drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o
FAILED: drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o 
ccache gcc -Idrivers/libtmp_rte_crypto_ipsec_mb.a.p -Idrivers -I../drivers
-Idrivers/crypto/ipsec_mb -I../drivers/crypto/ipsec_mb -Ilib/cryptodev
-I../lib/cryptodev -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/arm/include -I../lib/eal/arm/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 -Ilib/mbuf -I../lib/mbuf -Ilib/mempool
-I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu
-Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/net -I../lib/net -Ilib/security
-I../lib/security -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 -Wshadow -Wsign-compare
-Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned
-Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -mcpu=neoverse-n1
-DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation
-Wno-address-of-packed-member -Wno-vla -DRTE_COMPONENT_CLASS=pmd_crypto
-DRTE_COMPONENT_NAME=ipsec_mb -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.ipsec_mb -MD
-MQ drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o -MF
drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o.d -o
drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o -c
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c: In function ‘is_aead_algo’:
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:24:32: error: ‘IMB_CIPHER_SM4_GCM’
undeclared (first use in this function); did you mean ‘IMB_CIPHER_SM4_ECB’?
   24 |                 cipher_mode == IMB_CIPHER_SM4_GCM
      |                                ^~~~~~~~~~~~~~~~~~
      |                                IMB_CIPHER_SM4_ECB
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:24:32: note: each undeclared
identifier is reported only once for each function it appears in
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c: In function
‘aesni_mb_set_session_aead_parameters’:
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:716:50: error: ‘IMB_CIPHER_SM4_GCM’
undeclared (first use in this function); did you mean ‘IMB_CIPHER_SM4_ECB’?
  716 |                 sess->template_job.cipher_mode = IMB_CIPHER_SM4_GCM;
      |                                                  ^~~~~~~~~~~~~~~~~~
      |                                                  IMB_CIPHER_SM4_ECB
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:717:47: error: ‘IMB_AUTH_SM4_GCM’
undeclared (first use in this function); did you mean ‘IMB_AUTH_AES_CCM’?
  717 |                 sess->template_job.hash_alg = IMB_AUTH_SM4_GCM;
      |                                               ^~~~~~~~~~~~~~~~
      |                                               IMB_AUTH_AES_CCM
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:725:17: warning: implicit declaration
of function ‘imb_sm4_gcm_pre’ [-Wimplicit-function-declaration]
  725 |                 imb_sm4_gcm_pre(mb_mgr, xform->aead.key.data,
&sess->cipher.gcm_key);
      |                 ^~~~~~~~~~~~~~~
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:725:17: warning: nested extern
declaration of ‘imb_sm4_gcm_pre’ [-Wnested-externs]
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c: In function ‘set_cpu_mb_job_params’:
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:1055:14: error: ‘IMB_AUTH_SM4_GCM’
undeclared (first use in this function); did you mean ‘IMB_AUTH_AES_CCM’?
 1055 |         case IMB_AUTH_SM4_GCM:
      |              ^~~~~~~~~~~~~~~~
      |              IMB_AUTH_AES_CCM
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c: In function ‘set_mb_job_params’:
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:1607:14: error: ‘IMB_AUTH_SM4_GCM’
undeclared (first use in this function); did you mean ‘IMB_AUTH_AES_CCM’?
 1607 |         case IMB_AUTH_SM4_GCM:
      |              ^~~~~~~~~~~~~~~~
      |              IMB_AUTH_AES_CCM
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:1798:14: error: ‘IMB_CIPHER_SM4_GCM’
undeclared (first use in this function); did you mean ‘IMB_CIPHER_SM4_ECB’?
 1798 |         case IMB_CIPHER_SM4_GCM:
      |              ^~~~~~~~~~~~~~~~~~
      |              IMB_CIPHER_SM4_ECB
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c: In function ‘is_aead_algo’:
../drivers/crypto/ipsec_mb/pmd_aesni_mb.c:26:1: warning: control reaches end of
non-void function [-Wreturn-type]
   26 | }
      | ^

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

                 reply	other threads:[~2026-10-07 20:38 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-2050-3@https.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