From: David Aldrich <david.aldrich.ntml@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: users <users@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: How to build DPDK without usertools/dpdk-setup.sh?
Date: Wed, 11 Sep 2024 16:59:34 +0100 [thread overview]
Message-ID: <CAJK_ieg_YGdeUdHZMmxM=xLur_0haYY+9Aq0autLTdPtn74UWQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8w9w_-EtkY4B3ACfCR1vOXOY2HiJ4_HgaYCQK7F8rCkFg@mail.gmail.com>
Hi David
Thanks for your reply,
> The only trick is to pass a -Dprefix=$(pwd)/install and make your
> application use this directory.
meson -Dexamples=all -Dprefix="/" build
is doing what I need.
I do have a further problem. The resulting build has no pmd drivers.
It is probably relevant that the output of the first meson command
includes:
=================
Content Skipped
=================
libs:
drivers:
common/mvep: missing dependency, "libmusdk"
common/mlx5: missing dependency, "mlx5"
crypto/qat: missing dependency, libcrypto
net/af_xdp: missing dependency, "libbpf"
net/ipn3ke: missing dependency, "libfdt"
net/mlx4: missing dependency, "mlx4"
net/mlx5: missing internal dependency, "common_mlx5"
net/mvneta: missing dependency, "libmusdk"
net/mvpp2: missing dependency, "libmusdk"
etc.
Many of those libraries are installed, but not libmusdk. Is that
essential? (I am using a Broadwell NIC).
Best regards
David
next prev parent reply other threads:[~2024-09-11 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 13:39 David Aldrich
2024-09-11 15:52 ` David Marchand
2024-09-11 15:59 ` David Aldrich [this message]
2024-09-11 16:11 ` Richardson, Bruce
2024-09-11 17:01 ` David Aldrich
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='CAJK_ieg_YGdeUdHZMmxM=xLur_0haYY+9Aq0autLTdPtn74UWQ@mail.gmail.com' \
--to=david.aldrich.ntml@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=users@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).