DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: vivekanandi <v.o.s.openbook@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Addressing ninja build error message
Date: Fri, 9 May 2025 13:56:53 +0000	[thread overview]
Message-ID: <MW4PR11MB58725A73F8347E4C9B0C7C138E8AA@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAEmGFk9v4-QWRy1-N+jMkdM=iVv69xPRaKUzuxkTuD9OYJa5cQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

Hi Vivek,

Could you please send me meson-logs/meson-log.txt? It will tell me what version of libbpf you are using and some other useful info.
It looks to me that the af_xdp meson build is not correctly determining what libbpf functions are available in your environment.

As a side note, if you don't intend on using the af_xdp driver you can bypass its compilation by specifying -Ddisable_drivers=af_xdp during the meson build.

Thanks,
Ciara

From: vivekanandi <v.o.s.openbook@gmail.com>
Sent: Friday 18 April 2025 22:53
To: dev@dpdk.org
Subject: Addressing ninja build error message

Hello,
My name is Vivek. I'm a Computer Science major from Canada.

I was trying to install DPDK but encountered this error. I am familiar with BPF programming so tried to look into the compat.h file but the build/af_xdp directory was empty after I got the error message. I've attached a txt file that shows the terminal output
I ran the following scripts:
meson build
ninja -C build
Could you please direct me to the right direction for building DPDK properly? I am on Linux Mint. Are there dependencies that I should've instaslled?
Best Regards,
V

[-- Attachment #2: Type: text/html, Size: 4603 bytes --]

      parent reply	other threads:[~2025-05-09 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 21:52 vivekanandi
2025-05-05 13:58 ` David Marchand
2025-05-09 13:56 ` Loftus, Ciara [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=MW4PR11MB58725A73F8347E4C9B0C7C138E8AA@MW4PR11MB5872.namprd11.prod.outlook.com \
    --to=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=v.o.s.openbook@gmail.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).