From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, zhoumin@loongson.cn
Subject: |FAILURE| pw148425-148429 [RFC 5/5] test: remove unneeded memset
Date: Thu, 14 Nov 2024 02:28:57 +0800 [thread overview]
Message-ID: <202411131828.4ADISvH13179342@localhost.localdomain> (raw)
In-Reply-To: <20241113185720.28706-6-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/148429
_ninja build failure_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 13 Nov 2024 10:56:00 -0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: c5df7a373ad07413d9652479272cd16adf989b06
148425-148429 --> 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/librte_common_qat.so.25.0
cc -o drivers/librte_common_qat.so.25.0 drivers/librte_common_qat.so.25.0.p/meson-generated_.._rte_common_qat.pmd.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_qat_common.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_qat_qp.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_qat_device.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_qat_logs.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_qat_pf2vf.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_dev_qat_dev_gen1.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_dev_qat_dev_gen2.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_dev_qat_dev_gen3.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_dev_qat_dev_gen4.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_dev_qat_dev_gen5.c.o drivers/libtmp_rte_common_qat.a.p/common_qat_dev_qat_dev_gen_lce.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_qat_comp_pmd.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_qat_comp.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_dev_qat_comp_pmd_
gen1.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_dev_qat_comp_pmd_gen2.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_dev_qat_comp_pmd_gen3.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_dev_qat_comp_pmd_gen4.c.o drivers/libtmp_rte_common_qat.a.p/compress_qat_dev_qat_comp_pmd_gen5.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_crypto.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_sym_pmd_gen1.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_asym_pmd_gen1.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen2.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen3.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen4.c.o drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen5.c.o drivers/libtmp_rte_comm
on_qat.a.p/crypto_qat_dev_qat_crypto_pmd_gen!
_lce.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_common_qat.so.25 -Wl,--no-as-needed -pthread -lm -ldl -lnuma -lfdt '-Wl,-rpath,$ORIGIN/:$ORIGIN/../lib' -Wl,-rpath-link,/home/zhoumin/gh_dpdk/build/drivers -Wl,-rpath-link,/home/zhoumin/gh_dpdk/build/lib drivers/librte_bus_pci.so.25.0 lib/librte_eal.so.25.0 lib/librte_kvargs.so.25.0 lib/librte_log.so.25.0 lib/librte_telemetry.so.25.0 lib/librte_pci.so.25.0 lib/librte_cryptodev.so.25.0 lib/librte_mbuf.so.25.0 lib/librte_mempool.so.25.0 lib/librte_ring.so.25.0 lib/librte_rcu.so.25.0 lib/librte_net.so.25.0 lib/librte_compressdev.so.25.0 lib/librte_security.so.25.0 -Wl,--version-script=/home/zhoumin/gh_dpdk/drivers/version.map /usr/lib64/libcrypto.so -Wl,--end-group
/usr/bin/ld: drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o: in function `.L386':
qat_asym.c:(.text+0x29b0): undefined reference to `memset_s'
/usr/bin/ld: qat_asym.c:(.text+0x29c8): undefined reference to `memset_s'
/usr/bin/ld: qat_asym.c:(.text+0x29e8): undefined reference to `memset_s'
/usr/bin/ld: drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o: in function `.L381':
qat_asym.c:(.text+0x2a04): undefined reference to `memset_s'
/usr/bin/ld: qat_asym.c:(.text+0x2a1c): undefined reference to `memset_s'
/usr/bin/ld: drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o:qat_asym.c:(.text+0x2a60): more undefined references to `memset_s' follow
collect2: error: ld returned 1 exit status
[1238/2601] Generating rte_net_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[1239/2601] Compiling C object drivers/libtmp_rte_net_ena.a.p/net_ena_ena_ethdev.c.o
[1240/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_rss.c.o
[1241/2601] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_api_cmd.c.o
[1242/2601] Generating symbol file lib/librte_ethdev.so.25.0.p/librte_ethdev.so.25.0.symbols
[1243/2601] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_rxtx.c.o
[1244/2601] Compiling C object drivers/libtmp_rte_net_e1000.a.p/net_e1000_igb_ethdev.c.o
[1245/2601] Compiling C object drivers/net/fm10k/base/libfm10k_base.a.p/fm10k_mbx.c.o
[1246/2601] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_eqs.c.o
[1247/2601] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_cmdq.c.o
[1248/2601] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_hwif.c.o
[1249/2601] Generating rte_net_bnxt.pmd.c with a custom command
[1250/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_rx_dqo.c.o
[1251/2601] Generating symbol file lib/librte_ipsec.so.25.0.p/librte_ipsec.so.25.0.symbols
[1252/2601] Generating symbol file lib/librte_lpm.so.25.0.p/librte_lpm.so.25.0.symbols
[1253/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_base_gve_adminq.c.o
[1254/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_tx_dqo.c.o
[1255/2601] Compiling C object drivers/net/fm10k/base/libfm10k_base.a.p/fm10k_pf.c.o
[1256/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_rx.c.o
[1257/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_ethdev.c.o
[1258/2601] Compiling C object drivers/libtmp_rte_net_fm10k.a.p/net_fm10k_fm10k_rxtx.c.o
[1259/2601] Compiling C object drivers/libtmp_rte_net_gve.a.p/net_gve_gve_tx.c.o
[1260/2601] Generating rte_net_enic.pmd.c with a custom command
[1261/2601] Compiling C object drivers/libtmp_rte_net_failsafe.a.p/net_failsafe_failsafe_ops.c.o
[1262/2601] Compiling C object drivers/net/hinic/base/libhinic_base.a.p/hinic_pmd_hwdev.c.o
[1263/2601] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[1264/2601] Compiling C object drivers/libtmp_rte_net_hinic.a.p/net_hinic_hinic_pmd_ethdev.c.o
[1265/2601] Compiling C object drivers/libtmp_rte_net_fm10k.a.p/net_fm10k_fm10k_ethdev.c.o
[1266/2601] Compiling C object drivers/libtmp_rte_net_dpaa2.a.p/net_dpaa2_dpaa2_rxtx.c.o
[1267/2601] Compiling C object drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_ethdev.c.o
[1268/2601] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[1269/2601] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[1270/2601] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------
next parent reply other threads:[~2024-11-13 19:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241113185720.28706-6-stephen@networkplumber.org>
2024-11-13 18:28 ` qemudev [this message]
2024-11-13 18:59 ` |SUCCESS| pw148429 " checkpatch
2024-11-13 19:45 ` |FAILURE| " 0-day Robot
2024-11-13 21:00 ` |SUCCESS| pw148425-148429 [PATCH] [RFC,5/5] test: remove unneeded me dpdklab
2024-11-13 21:57 ` dpdklab
2024-11-13 22:58 ` dpdklab
2024-11-13 23:28 ` dpdklab
2024-11-13 23:59 ` |FAILURE| " dpdklab
2024-11-14 0:12 ` |WARNING| " dpdklab
2024-11-14 0:12 ` dpdklab
2024-11-14 0:31 ` |PENDING| " dpdklab
2024-11-14 0:49 ` |FAILURE| " dpdklab
2024-11-14 0:50 ` dpdklab
2024-11-14 0:52 ` dpdklab
2024-11-14 0:53 ` dpdklab
2024-11-14 0:54 ` |PENDING| " dpdklab
2024-11-14 0:54 ` |FAILURE| " dpdklab
2024-11-14 0:56 ` dpdklab
2024-11-14 0:59 ` dpdklab
2024-11-14 0:59 ` dpdklab
2024-11-14 0:59 ` dpdklab
2024-11-14 1:00 ` dpdklab
2024-11-14 1:00 ` dpdklab
2024-11-14 1:01 ` dpdklab
2024-11-14 1:01 ` dpdklab
2024-11-14 1:01 ` dpdklab
2024-11-14 1:01 ` dpdklab
2024-11-14 1:02 ` dpdklab
2024-11-14 1:02 ` |WARNING| " dpdklab
2024-11-14 1:03 ` dpdklab
2024-11-14 1:18 ` dpdklab
2024-11-14 1:18 ` dpdklab
2024-11-14 1:39 ` dpdklab
2024-11-14 2:02 ` |FAILURE| " dpdklab
2024-11-14 2:03 ` dpdklab
2024-11-14 2:04 ` dpdklab
2024-11-14 2:06 ` dpdklab
2024-11-14 2:21 ` |PENDING| " dpdklab
2024-11-14 2:22 ` |WARNING| " dpdklab
2024-11-14 2:23 ` dpdklab
2024-11-14 2:59 ` |FAILURE| " dpdklab
2024-11-14 3:07 ` dpdklab
2024-11-14 3:23 ` dpdklab
2024-11-14 3:23 ` dpdklab
2024-11-14 3:44 ` |WARNING| " dpdklab
2024-11-14 3:45 ` dpdklab
2024-11-14 4:24 ` |FAILURE| " dpdklab
2024-11-14 4:28 ` dpdklab
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=202411131828.4ADISvH13179342@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=stephen@networkplumber.org \
--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).