All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 896] [20.11.4-rc1] net/af_xdp build failure with gcc 11 on Fedora 35
Date: Wed, 08 Dec 2021 09:13:20 +0000	[thread overview]
Message-ID: <bug-896-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 896
           Summary: [20.11.4-rc1] net/af_xdp build failure with gcc 11 on
                    Fedora 35
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

I can reproduce the following build error on 20.11.4-rc1:

"""
$ meson --werror --buildtype=debugoptimized build && ninja-build -C build
[..]
drivers/net/af_xdp/rte_eth_af_xdp.c: In function 'load_custom_xdp_prog':
drivers/net/af_xdp/rte_eth_af_xdp.c:1065:15: error: implicit declaration of
function 'bpf_prog_load'; did you mean 'bpf_program__load'?
[-Werror=implicit-function-declaration]
 1065 |         ret = bpf_prog_load(prog_path, BPF_PROG_TYPE_XDP, &obj,
&prog_fd);
      |               ^~~~~~~~~~~~~
      |               bpf_program__load
drivers/net/af_xdp/rte_eth_af_xdp.c:1065:15: error: nested extern declaration
of 'bpf_prog_load' [-Werror=nested-externs]
cc1: all warnings being treated as errors
"""

OS: Fedora Linux 35 (Container Image)
gcc: 11.2.1 20210728 (Red Hat 11.2.1-1)

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

                 reply	other threads:[~2021-12-08  9:13 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-896-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.