From: Bruce Richardson <bruce.richardson@intel.com>
To: Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH] ci: add 32-bit travis builds
Date: Tue, 19 Nov 2019 15:15:43 +0000 [thread overview]
Message-ID: <20191119151543.54309-1-bruce.richardson@intel.com> (raw)
Add a travis job to build for 32-bit on 64-bit systems to catch additional
build errors, for example, incorrect use of printf specifiers with uint64_t
types.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
.ci/linux-build.sh | 5 +++++
.travis.yml | 10 ++++++++++
2 files changed, 15 insertions(+)
diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
index 6075c440c..c570ba24e 100755
--- a/.ci/linux-build.sh
+++ b/.ci/linux-build.sh
@@ -23,6 +23,11 @@ if [ "$BUILD_DOCS" = "1" ]; then
OPTS="$OPTS -Denable_docs=true"
fi
+if [ "$BUILD_32BIT" = "1" ]; then
+ OPTS="$OPTS -Dc_args=-m32 -Dc_link_args=-m32"
+ export PKG_CONFIG_LIBDIR="/usr/lib32/pkgconfig"
+fi
+
OPTS="$OPTS --default-library=$DEF_LIB"
meson build --werror -Dexamples=all $OPTS
ninja -C build
diff --git a/.travis.yml b/.travis.yml
index 3d6ef2959..7b9fc6898 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -23,6 +23,10 @@ extra_packages: &extra_packages
- *required_packages
- [libbsd-dev, libpcap-dev, libcrypto++-dev, libjansson4]
+build_32b_packages: &build_32b_packages
+ - *required_packages
+ - [gcc-multilib]
+
doc_packages: &doc_packages
- [doxygen, graphviz, python3-sphinx]
@@ -37,6 +41,12 @@ env:
matrix:
include:
+ - env: DEF_LIB="static" BUILD_32BIT=1
+ compiler: gcc
+ addons:
+ apt:
+ packages:
+ - *build_32b_packages
- env: DEF_LIB="static" OPTS="-Denable_kmods=false" AARCH64=1
compiler: gcc
addons:
--
2.21.0
next reply other threads:[~2019-11-19 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 15:15 Bruce Richardson [this message]
2019-11-19 16:06 ` Aaron Conole
2019-11-19 21:38 ` David Marchand
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=20191119151543.54309-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.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).