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: [PATCH 0/3] enable PPC in test-meson-builds on ubuntu
Date: Thu, 31 Aug 2023 13:10:55 +0100	[thread overview]
Message-ID: <20230831121058.725577-1-bruce.richardson@intel.com> (raw)

To help developers catch errors as soon as possible, we want to ensure
that as wide a variety of builds are done by test-meson-builds as
possible. Unfortunately, for those using Ubuntu, the shipped version
of GCC compiler for PowerPC on that system is not correctly detected by
the script. We fix this by detecting if Ubuntu is in use, and pointing
to the correct cross-file in that case.

On enabling those PPC builds on my system, a couple of other build
issues we encountered. These are fixed by the set before enabling the
build in the script.

Bruce Richardson (3):
  vhost: fix build for powerpc
  build: fix failures due to incompatible IPSec lib
  devtools: enable testing ppc builds on ubuntu

 devtools/test-meson-builds.sh       | 3 +++
 drivers/crypto/ipsec_mb/meson.build | 5 +++++
 lib/vhost/vduse.c                   | 9 ++++++---
 3 files changed, 14 insertions(+), 3 deletions(-)

--
2.39.2


             reply	other threads:[~2023-08-31 12:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 12:10 Bruce Richardson [this message]
2023-08-31 12:10 ` [PATCH 1/3] vhost: fix build for powerpc Bruce Richardson
2023-09-01 14:59   ` Bruce Richardson
2023-09-12 18:30     ` David Christensen
2023-09-29 14:47   ` Maxime Coquelin
2023-08-31 12:10 ` [PATCH 2/3] crypto/ipsec_mb: fix build failures due to incompatible lib Bruce Richardson
2023-08-31 13:18   ` Power, Ciara
2023-08-31 12:10 ` [PATCH 3/3] devtools: enable testing ppc builds on ubuntu Bruce Richardson
2023-09-01  1:16   ` Tyler Retzlaff
2023-10-11  9:14 ` [PATCH 0/3] enable PPC in test-meson-builds " Thomas Monjalon

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=20230831121058.725577-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).