From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: bluca@debian.org, jerin.jacob@caviumnetworks.com,
hemant.agrawal@nxp.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] Enable cross-compilation of DPDK with meson
Date: Tue, 19 Dec 2017 10:52:20 +0000 [thread overview]
Message-ID: <20171219105222.198664-1-bruce.richardson@intel.com> (raw)
While meson has built-in support for cross-compilation, there can be things
inside the meson.build files which cause problems in a cross-compile
environment. This patchset fixes a number of issues found when doing test
builds for arm architecture.
NOTE: this patchset only contains the fixes made to existing code. The
additional files needed for building for an arm target will be sent out as
an RFC patch separately, to be picked up by those more familiar with arm
architecture and hopefully turned into a production-ready patchset. The
resulting arm build was not test run on any platform.
Bruce Richardson (2):
build: remove architecture flag as default C flag
net/pcap: fix cross compilation
app/test-pmd/meson.build | 1 +
buildtools/pmdinfogen/meson.build | 3 +--
config/meson.build | 8 ++++++--
drivers/meson.build | 2 +-
drivers/net/i40e/meson.build | 2 +-
drivers/net/ixgbe/meson.build | 2 +-
drivers/net/pcap/meson.build | 21 +++++++++++++++------
examples/meson.build | 2 +-
lib/meson.build | 2 +-
meson.build | 2 +-
10 files changed, 29 insertions(+), 16 deletions(-)
--
2.14.3
next reply other threads:[~2017-12-19 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 10:52 Bruce Richardson [this message]
2017-12-19 10:52 ` [dpdk-dev] [PATCH 1/2] build: remove architecture flag as default C flag Bruce Richardson
2017-12-19 10:52 ` [dpdk-dev] [PATCH 2/2] net/pcap: fix cross compilation Bruce Richardson
2017-12-19 13:25 ` [dpdk-dev] [PATCH 0/2] Enable cross-compilation of DPDK with meson Luca Boccassi
2017-12-19 14:30 ` 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=20171219105222.198664-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).