dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: David Christensen <drc@linux.vnet.ibm.com>
To: maxime.coquelin@redhat.com, tiwei.bie@intel.com
Cc: dev@dpdk.org, David Christensen <drc@linux.vnet.ibm.com>
Subject: [dpdk-dev] [PATCH 0/2] fixes to resolve meson build issues on Power systems
Date: Wed, 14 Aug 2019 13:36:39 -0500	[thread overview]
Message-ID: <1565807801-72546-1-git-send-email-drc@linux.vnet.ibm.com> (raw)

Encountered a few issues while testing meson builds.  The first is related
to the gcc compiler used on RHEL 7.6 and how it interprets the "native" 
CPU type when running on a Power 9 system.  The second is a print format
warning error on Power systems.

David Christensen (2):
  config: fix RHEL7.6 build errors on Power 9 systems
  vhost: fix build error caused by 64bit print formatting

 config/ppc_64/meson.build     | 10 ++++++++++
 lib/librte_vhost/vhost_user.c |  9 +++++----
 2 files changed, 15 insertions(+), 4 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-08-14 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 18:36 David Christensen [this message]
2019-08-14 18:36 ` [dpdk-dev] [PATCH 1/2] config: fix RHEL7.6 build errors on Power 9 systems David Christensen
2019-10-25 18:52   ` David Christensen
2019-10-27 10:04   ` David Marchand
2019-08-14 18:36 ` [dpdk-dev] [PATCH 2/2] vhost: fix build error caused by 64bit print formatting David Christensen
2019-08-15  6:53   ` David Marchand
2019-08-15 16:16     ` David Christensen
2019-08-19  8:40       ` David Marchand
2019-08-19 11:41         ` Maxime Coquelin
2019-10-24 19:27           ` David Marchand
2019-10-25  4:38             ` Tiwei Bie
2019-10-25  4:41   ` Tiwei Bie
2019-10-27 10:04     ` 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=1565807801-72546-1-git-send-email-drc@linux.vnet.ibm.com \
    --to=drc@linux.vnet.ibm.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=tiwei.bie@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).