From: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
To: dev@dpdk.org
Cc: alejandro.lucero@netronome.com, allain.legacy@windriver.com,
jasvinder.singh@intel.com, keith.wiles@intel.com,
matan@mellanox.com, bruce.richardson@intel.com,
reshma.pattan@intel.com,
Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/6] fix for meson builds in freebsd
Date: Wed, 3 Oct 2018 15:00:15 +0100 [thread overview]
Message-ID: <1538575221-23873-1-git-send-email-agalyax.babu.radhakrishnan@intel.com> (raw)
In-Reply-To: <1538054652-20820-1>
Compilation issues were observed in FreeBSD when built via meson.
VFIO flags are enabled/disabled based on linux/freebsd.
Changes are done in meson.build files to ensure
the build of drivers are enabled/disabled based on platform.
1/6: set/unset of vfio flags based on platforms
2/6: updated net/nfp meson build
3/6: updated net/avp meson build
4/6: updated net/softnic meson build
5/6: updated net/tap meson build
6/6: updated net/vdev_netvsc meson build
Signed-off-by: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
--
v2: Added fixes line for the appropriate file
Updated meson.build changes to config instead of lib
--
Agalya Babu RadhaKrishnan (6):
build: fix for FREEBSD build via meson
net/nfp: disable nfp build in FREEBSD
net/avp: disable avp build in FREEBSD
net/softnic: disable softnic build in FREEBSD
net/tap: disable tap build in FREEBSD
net/vdev_netvsc: disable vdev netvsc build in FREEBSD
config/meson.build | 3 +++
config/rte_config.h | 1 -
drivers/net/avp/meson.build | 3 +++
drivers/net/nfp/meson.build | 3 +++
drivers/net/softnic/meson.build | 3 +++
drivers/net/tap/meson.build | 3 +++
drivers/net/vdev_netvsc/meson.build | 3 +++
7 files changed, 18 insertions(+), 1 deletion(-)
--
2.13.6
next parent reply other threads:[~2018-10-03 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1538054652-20820-1>
2018-10-03 14:00 ` Agalya Babu RadhaKrishnan [this message]
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 1/6] build: fix for FREEBSD build via meson Agalya Babu RadhaKrishnan
2018-10-03 15:42 ` Bruce Richardson
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 2/6] net/nfp: disable nfp build in FREEBSD Agalya Babu RadhaKrishnan
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 3/6] net/avp: disable avp " Agalya Babu RadhaKrishnan
2018-10-03 15:12 ` Legacy, Allain
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 4/6] net/softnic: disable softnic " Agalya Babu RadhaKrishnan
2018-10-03 15:36 ` Singh, Jasvinder
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 5/6] net/tap: disable tap " Agalya Babu RadhaKrishnan
2018-10-03 14:24 ` Wiles, Keith
2018-10-03 14:00 ` [dpdk-dev] [PATCH v2 6/6] net/vdev_netvsc: disable vdev netvsc " Agalya Babu RadhaKrishnan
2018-10-03 15:10 ` Stephen Hemminger
[not found] ` <1538574386-21771-2-git-send-email-agalyabx@wgcvswdev001.ir.intel.com>
2018-10-03 15:33 ` [dpdk-dev] [PATCH v2 1/6] build: fix for FREEBSD build via meson 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=1538575221-23873-1-git-send-email-agalyax.babu.radhakrishnan@intel.com \
--to=agalyax.babu.radhakrishnan@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=allain.legacy@windriver.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=keith.wiles@intel.com \
--cc=matan@mellanox.com \
--cc=reshma.pattan@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).