From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1083] crypto/openssl build failure in Ubuntu 22.04
Date: Thu, 22 Sep 2022 12:43:47 +0000 [thread overview]
Message-ID: <bug-1083-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1083
Bug ID: 1083
Summary: crypto/openssl build failure in Ubuntu 22.04
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror build && ninja -C build
[2219/3281] Compiling C object
drivers/libtmp_rte...to_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o
FAILED:
drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o
ccache cc -Idrivers/libtmp_rte_crypto_openssl.a.p -Idrivers -I../drivers
-Idrivers/crypto/openssl -I../drivers/crypto/openssl -Ilib/cryptodev
-I../lib/cryptodev -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 -Ilib/eal/common
-I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs
-Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -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
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra
-Werror -O3 -include rte_config.h -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-address-of-packed-member -Wno-packed-not-aligned
-Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC
-march=armv8-a+crc -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API
-Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.crypto.openssl -MD -MQ
drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o -MF
drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o.d -o
drivers/libtmp_rte_crypto_openssl.a.p/crypto_openssl_rte_openssl_pmd.c.o -c
../drivers/crypto/openssl/rte_openssl_pmd.c
In file included from /usr/include/string.h:535,
from ../lib/eal/include/rte_uuid.h:19,
from ../lib/eal/include/rte_eal.h:21,
from ../lib/eal/include/rte_lcore.h:16,
from ../lib/eal/include/generic/rte_spinlock.h:21,
from ../lib/eal/arm/include/rte_spinlock.h:17,
from ../lib/mempool/rte_mempool.h:41,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/cryptodev/rte_crypto.h:20,
from ../lib/cryptodev/rte_cryptodev.h:22,
from ../drivers/crypto/openssl/rte_openssl_pmd.c:7:
In function 'memcpy',
inlined from 'openssl_set_session_auth_parameters' at
../drivers/crypto/openssl/rte_openssl_pmd.c:654:3,
inlined from 'openssl_set_session_parameters' at
../drivers/crypto/openssl/rte_openssl_pmd.c:781:
:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: error:
'__builtin_memcpy' forming offset [4, 8] is out of the bounds [0, 4]
[-Werror=array-bounds]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 | __glibc_objsize0 (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[2267/3281] Generating lib/eal.sym_chk with a custom command (wrapped by meson
to capture output)
ninja: build stopped: subcommand failed.
"""
Reproduces on main (72b452c5f259).
Environment:
OS: Ubuntu 22.04.1
architecture: aarch64
gcc: 11.2.0-19ubuntu1
meson: 0.63.2
ninja-build: 1.10.1
libssl: 3.0.2-0ubuntu1.6
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-09-22 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 12:43 bugzilla [this message]
2023-06-20 8:09 ` [Bug 1083] [aarch64] crypto/openssl build failure in Ubuntu 22.04 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-1083-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.