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: Fri, 14 Oct 2022 10:24:26 +0000	[thread overview]
Message-ID: <bug-1076-3-AtgGo1SkP3@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1076-3@http.bugs.dpdk.org/>

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

Ferruh YIGIT (ferruhy@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
         Resolution|INVALID                     |---
                 CC|                            |ferruhy@gmail.com
             Status|RESOLVED                    |CONFIRMED

--- Comment #2 from Ferruh YIGIT (ferruhy@gmail.com) ---
Hi Daxue,

The problem is neither related to the compiler version nor the commit listed
above, it should be related to the kernel version.

The related build error fixed in commit:
c98600d4bed6 ("kni: fix build with Linux 5.18")

Starting with kernel version 5.18, 'netif_rx_ni()' function is removed from
kernel.

Having a build error with RHEL9.0/5.14.0-160.el9.x86_64 kernel means it
backported related kernel commit.


So, I expect the issue is still valid and it needs a special RHEL version check
in KNI.

Can you please double check with RHEL9 again?

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

      parent reply	other threads:[~2022-10-14 10:24 UTC|newest]

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

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-AtgGo1SkP3@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).