From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Nithinsen Kaithakadan <nkaithakadan@marvell.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw154522 [PATCH] crypto/cnxk: add crypto adapter for cn20k
Date: Tue, 17 Jun 2025 18:41:19 +0800 [thread overview]
Message-ID: <202506171041.55HAfJx13341009@localhost.localdomain> (raw)
In-Reply-To: <20250617105823.105906-1-nkaithakadan@marvell.com>
Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/154522
_ninja build failure_
Submitter: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
Date: Tue, 17 Jun 2025 10:58:23 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: dbeb8ae8d09387bd525353f4a5aa6ec152cddffa
154522 --> ninja build failed
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
Ninja build logs:
-------------------------------BEGIN LOGS----------------------------
FAILED: drivers/rte_crypto_cnxk.sym_chk
/usr/local/bin/meson --internal exe --capture drivers/rte_crypto_cnxk.sym_chk -- /home/zhoumin/gh_dpdk/buildtools/check-symbols.sh /home/zhoumin/gh_dpdk/build/drivers/crypto_cnxk_exports.map drivers/librte_crypto_cnxk.a
--- stderr ---
cn20k_cpt_crypto_adapter_dequeue is flagged as internal but is not exported as an internal symbol
Please add RTE_EXPORT_INTERNAL_SYMBOL to the definition of cn20k_cpt_crypto_adapter_dequeue
cn20k_cpt_crypto_adapter_vector_dequeue is flagged as internal but is not exported as an internal symbol
Please add RTE_EXPORT_INTERNAL_SYMBOL to the definition of cn20k_cpt_crypto_adapter_vector_dequeue
cn20k_cpt_crypto_adapter_enqueue is flagged as internal but is not exported as an internal symbol
Please add RTE_EXPORT_INTERNAL_SYMBOL to the definition of cn20k_cpt_crypto_adapter_enqueue
[2943/2967] Linking target app/dpdk-test-security-perf
[2944/2967] Linking target app/dpdk-dumpcap
[2945/2967] Linking target app/dpdk-test-acl
[2946/2967] Linking target app/dpdk-test-flow-perf
[2947/2967] Linking target app/dpdk-testpmd
[2948/2967] Linking target app/dpdk-test-gpudev
[2949/2967] Linking target app/dpdk-graph
[2950/2967] Linking target app/dpdk-test-fib
[2951/2967] Linking target app/dpdk-test-pipeline
[2952/2967] Linking target app/dpdk-test-crypto-perf
[2953/2967] Linking target app/dpdk-test-regex
[2954/2967] Linking target app/dpdk-proc-info
[2955/2967] Linking target app/dpdk-test-sad
[2956/2967] Linking target app/dpdk-test-mldev
[2957/2967] Linking target app/dpdk-test-eventdev
[2958/2967] Linking target app/dpdk-test-cmdline
[2959/2967] Linking target app/dpdk-test-bbdev
[2960/2967] Linking target app/dpdk-pdump
[2961/2967] Linking target app/dpdk-test-compress-perf
[2962/2967] Linking target app/dpdk-test-dma-perf
[2963/2967] Compiling C object app/dpdk-test.p/test_test_ring.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------
next parent reply other threads:[~2025-06-17 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250617105823.105906-1-nkaithakadan@marvell.com>
2025-06-17 10:41 ` qemudev [this message]
2025-06-17 10:59 ` |WARNING| " checkpatch
2025-06-17 11:35 ` |FAILURE| " dpdklab
2025-06-17 12:05 ` 0-day Robot
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=202506171041.55HAfJx13341009@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=nkaithakadan@marvell.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).