DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1076] [dpdk 22.11] kernel/linux/kni meson build failed with gcc 11.3.1  on rhel9.0
Date: Wed, 07 Sep 2022 06:46:47 +0000	[thread overview]
Message-ID: <bug-1076-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1076
           Summary: [dpdk 22.11] kernel/linux/kni meson build failed with
                    gcc 11.3.1  on rhel9.0
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: daxuex.gao@intel.com
  Target Milestone: ---

[DPDK version]:
commit 4aee6110bb10b0225fa9562f2e48af233a9058a1 (HEAD -> main, origin/main,
origin/HEAD)
Author: Huichao Cai <chcchc88@163.com>
Date:   Mon Aug 8 09:48:12 2022 +0800

    ip_frag: add IPv4 fragment copy

    Some NIC drivers support MBUF_FAST_FREE (device supports optimization
    for fast release of mbufs. When set, application must guarantee that
    per-queue all mbufs comes from the same mempool, has refcnt = 1, direct
    and non-segmented.) offload.
    In order to adapt to this offload function, add this API.
    Add some test data for this API.

    Signed-off-by: Huichao Cai <chcchc88@163.com>
    Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>


[OS version]:
RHEL9.0/5.14.0-160.el9.x86_64
gcc version 11.3.1 20220421

[Test Setup]:
CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all
--default-library=static x86_64-native-linuxapp-gcc 
ninja -j 10 -C x86_64-native-linuxapp-gcc/

[Log]
FAILED: kernel/linux/kni/rte_kni.ko
/usr/bin/make -j4 -C /lib/modules/5.14.0-160.el9.x86_64/build
M=/root/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni
src=/root/dpdk/kernel/linux/kni 'MODULE_CFLAGS= -DHAVE_ARG_TX_QUEUE -include
/root/dpdk/config/rte_config.h -I/root/dpdk/lib/eal/include
-I/root/dpdk/lib/kni -I/root/dpdk/x86_64-native-linuxapp-gcc
-I/root/dpdk/kernel/linux/kni' modules
make: Entering directory '/usr/src/kernels/5.14.0-160.el9.x86_64'
  CC [M]  /root/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni/kni_misc.o
  CC [M]  /root/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni/kni_net.o
/root/dpdk/kernel/linux/kni/kni_net.c: In function ‘kni_net_rx_normal’:
/root/dpdk/kernel/linux/kni/kni_net.c:445:17: error: implicit declaration of
function ‘netif_rx_ni’; did you mean ‘netif_rx’?
[-Werror=implicit-function-declaration]
  445 |                 netif_rx_ni(skb);
      |                 ^~~~~~~~~~~
      |                 netif_rx
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:295:
/root/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni/kni_net.o] Error 1
make: *** [Makefile:1915:
/root/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni] Error 2
make: Leaving directory '/usr/src/kernels/5.14.0-160.el9.x86_64'
ninja: build stopped: subcommand failed.


[Bad commit]
This is new os found problem, old os no found problem.

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

             reply	other threads:[~2022-09-07  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  6:46 bugzilla [this message]
2022-09-22  5:27 ` bugzilla
2022-10-14 10:24 ` 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-1076-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).