DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ciara Power <ciara.power@intel.com>
Cc: dev@dpdk.org, akhil.goyal@nxp.com, hemant.agrawal@nxp.com
Subject: Re: [dpdk-dev] [PATCH] crypto/dpaa2_sec: fix build with clang 3.4.2
Date: Fri, 01 Nov 2019 22:34:29 +0100	[thread overview]
Message-ID: <16554965.ArIabKrkQH@xps> (raw)
In-Reply-To: <20191031140552.62117-1-ciara.power@intel.com>

31/10/2019 15:05, Ciara Power:
> Building with clang 3.4.2 caused the following error:
> 
>   CC dpaa2_sec_dpseci.o
> In file included from /dpdk/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:40:
> In file included from /dpdk/drivers/common/dpaax/caamflib/desc/ipsec.h:11:
> In file included from /dpdk/drivers/common/dpaax/caamflib/rta.h:11:
> In file included from .../common/dpaax/caamflib/rta/sec_run_time_asm.h:14:
> /dpdk/drivers/common/dpaax/compat.h:108:18:
> error: redefinition of typedef 'dma_addr_t' is a C11 feature
> [-Werror,-Wtypedef-redefinition]
> typedef uint64_t        dma_addr_t;
>                         ^
> /dpdk/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:37:18:
> note: previous definition is here
> typedef uint64_t        dma_addr_t;
>                         ^
> 1 error generated.
> 
> The dma_addr_t was defined in the common compat.h file, and does not
> need to be redefined.
> 
> The meson build include directories list was updated to enable the
> definition in the common compat.h file be used.
> 
> Fixes: 8c83f28cc8a4 ("common/dpaax: move OF library from DPAA bus")
> Cc: hemant.agrawal@nxp.com
> 
> Signed-off-by: Ciara Power <ciara.power@intel.com>

Applied, thanks




      parent reply	other threads:[~2019-11-01 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 14:05 Ciara Power
2019-11-01  5:25 ` Hemant Agrawal
2019-11-01 21:34 ` Thomas Monjalon [this message]

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=16554965.ArIabKrkQH@xps \
    --to=thomas@monjalon.net \
    --cc=akhil.goyal@nxp.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).