From: David Christensen <drc@linux.vnet.ibm.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
matan@mellanox.com, shahafs@mellanox.com
Cc: dev <dev@dpdk.org>, Luca Boccassi <bluca@debian.org>,
Thomas Monjalon <thomas@monjalon.net>,
Frank Heimes <frank.heimes@canonical.com>
Subject: Re: [dpdk-dev] [PATCH 1/1] net/mlx4: fix build on PPC64
Date: Thu, 29 Aug 2019 10:06:08 -0700 [thread overview]
Message-ID: <b305d19e-a236-d933-71a4-b21a5d5e00f6@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAATJJ0LXa3VEvczus3XPTy6qNPZYoV-3SH7DmDrD0m77eHuKwQ@mail.gmail.com>
>>> error: incompatible types when initializing type
>>> '__vector _bool int' {aka '_vector(4) __bool int'} using type 'int'
>>>
>>> If __APPLE_ALTIVEC__ is defined, then bool type is redefined
>>> and conflicts with stdbool.h.
>>>
>>> There is no good solution to fix it for the whole project without
>>> breaking something else, so a workaround is inserted in mlx5 PMD.
>>> This workaround is not compatible with C++ but there is no C++ in DPDK.
>>>
>>> Related to:
>>> https://git.dpdk.org/dpdk/commit/?id=725f5dd0bfb50192a2d2341d4cc69084c2c4e03d
>>>
>>> Change-Id: Iceb058c07086def4176c5ab199ca4dd5018d0340
>>> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>>
>> Tested-by: David Christensen <drc@linux.vnet.ibm.com>
>
> Thanks David, ping for considering inclusion into 19.11 ?
Yes please. I had the same patch ready to submit but you beat me to the
punch.
Dave
next prev parent reply other threads:[~2019-08-29 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 11:28 [dpdk-dev] [PATCH 0/1] PPC64 buid error in 19.08 Christian Ehrhardt
2019-08-13 11:28 ` [dpdk-dev] [PATCH 1/1] net/mlx4: fix build on PPC64 Christian Ehrhardt
2019-08-13 23:49 ` David Christensen
2019-08-28 12:30 ` Christian Ehrhardt
2019-08-29 17:06 ` David Christensen [this message]
2019-09-01 13:52 ` Matan Azrad
2019-09-02 10:12 ` Raslan Darawsheh
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=b305d19e-a236-d933-71a4-b21a5d5e00f6@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=frank.heimes@canonical.com \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
/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).