DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/5] Fix meson build on FreeBSD
Date: Thu,  1 Feb 2018 14:20:06 +0000	[thread overview]
Message-ID: <20180201142011.133441-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20180131174249.257933-1-bruce.richardson@intel.com>

There are a few issues with building DPDK for FreeBSD using the
meson build system, specifically:
* the kernel modules aren't compiling due to an incorrect VPATH
* a number of unit tests depend on libraries not supported on BSD
* applications and examples need to be linked with execinfo library.

----
V2: merged patch 6 in with patch 2, since it's the same fix for main apps
    and for the examples.

Bruce Richardson (5):
  eal/bsdapp: fix building kernel modules
  build: fix dependency on execinfo for BSD meson builds
  test/test: mark tests as skipped when required lib not available
  test/test: fix dependency on power lib for BSD meson build
  test/test: fix dependency on KNI lib for BSD meson build

 app/test-eventdev/meson.build           |  1 +
 app/test-pmd/meson.build                |  1 +
 examples/meson.build                    |  3 ++-
 lib/librte_eal/bsdapp/BSDmakefile.meson |  1 +
 lib/librte_eal/meson.build              |  1 -
 test/test/meson.build                   |  8 +++++++-
 test/test/test_kni.c                    | 13 +++++++++++++
 test/test/test_power.c                  | 12 ++++++++++++
 test/test/test_power_acpi_cpufreq.c     | 11 +++++++++++
 test/test/test_power_kvm_vm.c           | 11 +++++++++++
 10 files changed, 59 insertions(+), 3 deletions(-)

-- 
2.14.1

  parent reply	other threads:[~2018-02-01 14:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 17:42 [dpdk-dev] [PATCH 0/6] " Bruce Richardson
2018-01-31 17:42 ` [dpdk-dev] [PATCH 1/6] eal/bsdapp: fix building kernel modules Bruce Richardson
2018-01-31 17:42 ` [dpdk-dev] [PATCH 2/6] build: add dependency on execinfo for BSD meson builds Bruce Richardson
2018-01-31 17:42 ` [dpdk-dev] [PATCH 3/6] test/test: mark tests as skipped when required lib not available Bruce Richardson
2018-02-01 16:32   ` Hunt, David
2018-01-31 17:42 ` [dpdk-dev] [PATCH 4/6] test/test: fix dependency on power lib for BSD meson build Bruce Richardson
2018-01-31 17:42 ` [dpdk-dev] [PATCH 5/6] test/test: fix dependency on KNI " Bruce Richardson
2018-01-31 17:42 ` [dpdk-dev] [PATCH 6/6] examples: fix meson build on FreeBSD Bruce Richardson
2018-02-01 14:20 ` Bruce Richardson [this message]
2018-02-01 14:20   ` [dpdk-dev] [PATCH v2 1/5] eal/bsdapp: fix building kernel modules Bruce Richardson
2018-02-01 14:20   ` [dpdk-dev] [PATCH v2 2/5] build: fix dependency on execinfo for BSD meson builds Bruce Richardson
2018-02-01 14:20   ` [dpdk-dev] [PATCH v2 3/5] test/test: mark tests as skipped when required lib not available Bruce Richardson
2018-02-01 14:20   ` [dpdk-dev] [PATCH v2 4/5] test/test: fix dependency on power lib for BSD meson build Bruce Richardson
2018-02-01 14:20   ` [dpdk-dev] [PATCH v2 5/5] test/test: fix dependency on KNI " Bruce Richardson
2018-02-02 11:11   ` [dpdk-dev] [PATCH v2 0/5] Fix meson build on FreeBSD Bruce Richardson

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=20180201142011.133441-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --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).