DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
To: dev@dpdk.org, ciara.loftus@intel.com, bruce.richardson@intel.com
Cc: qi.z.zhang@intel.com, john.mcnamara@intel.com,
	Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
Subject: [PATCH] net/af_xdp: pass cflags to appropriate build components
Date: Thu, 21 Sep 2023 10:29:23 +0000	[thread overview]
Message-ID: <20230921102923.65738-1-shibin.koikkara.reeny@intel.com> (raw)

Commit 33d66940e9ba ("build: use C11 standard") enforces
the C11 standard so some changes need to be made to the
af_xdp driver meson build to ensure that the appropriate
cflags are passed when checking if certain functions are
available in the libbpf/libxdp libraries.

Fixes: 33d66940e9ba ("build: use C11 standard")

Signed-off-by: Shibin Koikkara Reeny <shibin.koikkara.reeny@intel.com>
---
 drivers/net/af_xdp/meson.build | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/net/af_xdp/meson.build b/drivers/net/af_xdp/meson.build
index 9a8dbb4d49..3319acca65 100644
--- a/drivers/net/af_xdp/meson.build
+++ b/drivers/net/af_xdp/meson.build
@@ -56,17 +56,17 @@ if build
   '''
 
   if cc.has_function('xsk_socket__create_shared', prefix : xsk_check_prefix,
-                     dependencies : ext_deps)
+                     dependencies : ext_deps, args: cflags)
       cflags += ['-DRTE_NET_AF_XDP_SHARED_UMEM']
   endif
   if cc.has_function('bpf_object__next_program',
                      prefix : '#include <bpf/libbpf.h>',
-                     dependencies : bpf_dep)
+                     dependencies : bpf_dep, args: cflags)
       cflags += ['-DRTE_NET_AF_XDP_LIBBPF_OBJ_OPEN']
   endif
   if cc.has_function('bpf_xdp_attach',
                      prefix : '#include <bpf/libbpf.h>',
-                     dependencies : bpf_dep)
+                     dependencies : bpf_dep, args: cflags)
       cflags += ['-DRTE_NET_AF_XDP_LIBBPF_XDP_ATTACH']
   endif
 endif
-- 
2.25.1


             reply	other threads:[~2023-09-21 10:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 10:29 Shibin Koikkara Reeny [this message]
2023-09-21 10:43 ` Bruce Richardson
2023-09-21 10:47 ` Bruce Richardson
2023-09-22  9:31 ` [PATCH v2] net/af_xdp: fix cflags to appropriate UMEM feature Shibin Koikkara Reeny
2023-09-28  9:25   ` [PATCH v3] net/af_xdp: fix missing " Shibin Koikkara Reeny
2023-09-28  9:32     ` Bruce Richardson
2023-09-29 11:45       ` Ferruh Yigit
2023-10-02 12:48     ` [PATCH v4] " Shibin Koikkara Reeny
2023-10-02 13:01       ` Bruce Richardson
2023-10-02 13:15         ` Ferruh Yigit
2023-10-02 13:23           ` Bruce Richardson
2023-10-03  9:36             ` Ferruh Yigit

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=20230921102923.65738-1-shibin.koikkara.reeny@intel.com \
    --to=shibin.koikkara.reeny@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=qi.z.zhang@intel.com \
    /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).