automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Sunyang Wu <sunyang.wu@jaguarmicro.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw124564 [PATCH] crypto/openssl: support SM3/SM4 in openssl
Date: Wed, 1 Mar 2023 16:20:46 +0800	[thread overview]
Message-ID: <202303010820.3218KkCH953286@localhost.localdomain> (raw)
In-Reply-To: <20230228085410.27972-1-sunyang.wu@jaguarmicro.com>

Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/124564

_ninja build failure_

Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Tue, 28 Feb 2023 16:54:10 +0800
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 2ff0df42bf84113267ef76542e47d9b0e1a78705

124564 --> 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_crypto_openssl.so.23.1
cc -o drivers/librte_crypto_openssl.so.23.1 drivers/librte_crypto_openssl.so.23.1.p/meson-generated_.._rte_crypto_openssl.pmd.c.o drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd_ops.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_crypto_openssl.so.23 -Wl,--no-as-needed -pthread -lm -ldl -lnuma -lfdt lib/librte_cryptodev.so.23.1 lib/librte_eal.so.23.1 lib/librte_kvargs.so.23.1 lib/librte_telemetry.so.23.1 lib/librte_mbuf.so.23.1 lib/librte_mempool.so.23.1 lib/librte_ring.so.23.1 lib/librte_rcu.so.23.1 drivers/librte_bus_vdev.so.23.1 -Wl,--version-script=/home/zhoumin/dpdk-next-crypto/drivers/version.map /usr/lib64/libcrypto.so -Wl,--end-group '-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/' -Wl,-rpath-link,/home/zhoumin/dpdk-next-crypto/build/lib -Wl,-rpath-link,/home/zhoumin/dpdk-next-crypto/build/drivers
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L431':
rte_openssl_pmd.c:(.text+0x212c): undefined reference to `EVP_sm4_ecb'
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L432':
rte_openssl_pmd.c:(.text+0x2150): undefined reference to `EVP_sm4_ecb'
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L428':
rte_openssl_pmd.c:(.text+0x215c): undefined reference to `EVP_sm4_ctr'
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L430':
rte_openssl_pmd.c:(.text+0x218c): undefined reference to `EVP_sm4_cbc'
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L498':
rte_openssl_pmd.c:(.text+0x2270): undefined reference to `EVP_sm4_ecb'
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L442':
rte_openssl_pmd.c:(.text+0x2284): undefined reference to `EVP_sm4_ecb'
/usr/bin/ld: drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o: in function `.L441':
rte_openssl_pmd.c:(.text+0x2298): undefined reference to `EVP_sm4_ecb'
collect2: error: ld returned 1 exit status
[1979/2819] Linking static target drivers/librte_crypto_scheduler.a
[1980/2819] Compiling C object drivers/librte_crypto_scheduler.so.23.1.p/meson-generated_.._rte_crypto_scheduler.pmd.c.o
[1981/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_48_63_tmo_burst.c.o
[1982/2819] Generating symbol file drivers/librte_crypto_octeontx.so.23.1.p/librte_crypto_octeontx.so.23.1.symbols
[1983/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_32_47_seg.c.o
[1984/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_112_127_tmo_seg_burst.c.o
[1985/2819] Generating rte_crypto_caam_jr.pmd.c with a custom command
[1986/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cnxk_eventdev_selftest.c.o
[1987/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_0_15_seg.c.o
[1988/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_48_63_seg.c.o
[1989/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_0_15_tmo.c.o
[1990/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_32_47_tmo.c.o
[1991/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_96_111_tmo_seg_burst.c.o
[1992/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_96_111.c.o
[1993/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_16_31_tmo.c.o
[1994/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_80_95.c.o
[1995/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_112_127.c.o
[1996/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_0_15_ca.c.o
[1997/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_48_63_tmo.c.o
[1998/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_64_79.c.o
[1999/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_96_111_seg.c.o
[2000/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_112_127_seg.c.o
[2001/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_64_79_seg.c.o
[2002/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_80_95_seg.c.o
[2003/2819] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[2004/2819] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[2005/2819] Compiling C object drivers/libtmp_rte_crypto_dpaa2_sec.a.p/crypto_dpaa2_sec_dpaa2_sec_dpseci.c.o
[2006/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_64_79_tmo.c.o
[2007/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_96_111_tmo.c.o
[2008/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_112_127_tmo.c.o
[2009/2819] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn9k_deq_80_95_tmo.c.o
[2010/2819] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn9k_cryptodev_ops.c.o
[2011/2819] Compiling C object drivers/libtmp_rte_crypto_cnxk.a.p/crypto_cnxk_cn10k_cryptodev_ops.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------


  parent reply	other threads:[~2023-03-01  8:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230228085410.27972-1-sunyang.wu@jaguarmicro.com>
2023-02-28  8:54 ` |SUCCESS| " checkpatch
2023-02-28 10:19 ` |FAILURE| " 0-day Robot
2023-03-01  8:20 ` qemudev [this message]
2023-02-28 11:47 dpdklab
2023-02-28 11:53 dpdklab
2023-02-28 11:55 dpdklab
2023-02-28 11:56 dpdklab
2023-02-28 11:57 dpdklab
2023-02-28 12:01 dpdklab
2023-02-28 12:01 dpdklab
2023-02-28 12:10 dpdklab
2023-02-28 12:11 dpdklab
2023-02-28 12:12 dpdklab
2023-02-28 12:12 dpdklab
2023-02-28 12:13 dpdklab
2023-02-28 12:15 dpdklab
2023-02-28 12:16 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=202303010820.3218KkCH953286@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=sunyang.wu@jaguarmicro.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).