DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 985] [20.11] librte_eal build error with gcc 12
Date: Tue, 29 Mar 2022 14:40:36 +0000	[thread overview]
Message-ID: <bug-985-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 985
           Summary: [20.11] librte_eal build error with gcc 12
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

"""
$ meson --werror build && ninja-build -C build

[108/1974] Compiling C object
lib/librte_eal.a.p/librte_eal_linux_eal_eal_memory.c.o
FAILED: lib/librte_eal.a.p/librte_eal_linux_eal_eal_memory.c.o
gcc -Ilib/librte_eal.a.p -Ilib -I../../root/dpdk/lib -I. -I../../root/dpdk
-Iconfig -I../../root/dpdk/config -Ilib/librte_eal/common/include
-I../../root/dpdk/lib/librte_eal/common/include
-I../../root/dpdk/lib/librte_eal/linux/eal/include -Ilib/librte_eal/common
-I../../root/dpdk/lib/librte_eal/common
-Ilib/librte_eal/common/include/arch/x86
-I../../root/dpdk/lib/librte_eal/common/include/arch/x86 -Ilib/librte_eal
-I../../root/dpdk/lib/librte_eal -Ilib/librte_kvargs
-I../../root/dpdk/lib/librte_kvargs -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=native -Wno-format-truncation -DRTE_LIBEAL_USE_GETENTROPY
-DALLOW_EXPERIMENTAL_API -MD -MQ
lib/librte_eal.a.p/librte_eal_linux_eal_eal_memory.c.o -MF
lib/librte_eal.a.p/librte_eal_linux_eal_eal_memory.c.o.d -o
lib/librte_eal.a.p/librte_eal_linux_eal_eal_memory.c.o -c
../../root/dpdk/lib/librte_eal/linux/eal/eal_memory.c
In function 'eal_get_hugepage_mem_size',
    inlined from 'eal_legacy_hugepage_init' at
../../root/dpdk/lib/librte_eal/linux/eal/eal_memory.c:1566:28:
../../root/dpdk/lib/librte_eal/linux/eal/eal_memory.c:1272:21: error: 'strnlen'
specified bound 4096 exceeds source size 136 [-Werror=stringop-overread]
 1272 |                 if (strnlen(hpi->hugedir, sizeof(hpi->hugedir)) != 0) {
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../../root/dpdk/lib/librte_eal/linux/eal/eal_memory.c:49:
../../root/dpdk/lib/librte_eal/common/eal_internal_cfg.h: In function
'eal_legacy_hugepage_init':
../../root/dpdk/lib/librte_eal/common/eal_internal_cfg.h:86:31: note: source
object allocated here
   86 | extern struct internal_config internal_config; /**< Global EAL
configuration. */
      |                               ^~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[109/1974] Generating lib/timer_def with a custom command
"""

OS: Fedora Linux 37
gcc: 12.0.1 20220308 (Red Hat 12.0.1-0)

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

                 reply	other threads:[~2022-03-29 14:40 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-985-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 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).