DPDK usage discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
	"users@dpdk.org" <users@dpdk.org>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-users] fslmc bus compiling error
Date: Thu, 1 Aug 2019 03:43:19 +0000	[thread overview]
Message-ID: <VI1PR0401MB25412FABE86E86B50E7359D389DE0@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR08MB537631AB25F41B8880DCCA988FDF0@VI1PR08MB5376.eurprd08.prod.outlook.com>

HI Gavin,
	No we have not seen it before. Let me know your compilation steps and Git commit you are using to reproduce it.

Regards,
Hemant

> -----Original Message-----
> From: Gavin Hu (Arm Technology China) <Gavin.Hu@arm.com>
> Sent: Wednesday, July 31, 2019 9:05 PM
> To: Hemant Agrawal <hemant.agrawal@nxp.com>; users@dpdk.org
> Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; nd
> <nd@arm.com>
> Subject: fslmc bus compiling error
> 
> Hi Hemant,
> 
> There are two "dmb" functions defined and they are conflicting with each
> other. Did you notice this compiling error?
> 
>   CC base/qbman/dpaa_alloc.o
> In file included from /home/gavin/dpdk/build/include/rte_atomic.h:9,
>                  from /home/gavin/dpdk/build/include/generic/rte_pause.h:16,
>                  from /home/gavin/dpdk/build/include/rte_pause_64.h:13,
>                  from /home/gavin/dpdk/build/include/rte_pause.h:13,
>                  from /home/gavin/dpdk/build/include/generic/rte_spinlock.h:25,
>                  from /home/gavin/dpdk/build/include/rte_spinlock.h:17,
>                  from /home/gavin/dpdk/drivers/bus/fslmc/mc/mc_sys.c:10:
> /home/gavin/dpdk/build/include/rte_atomic_64.h:19: error: "dmb"
> redefined [-Werror]  #define dmb(opt) asm volatile("dmb " #opt : : :
> "memory")
> 
> In file included from /home/gavin/dpdk/drivers/bus/fslmc/mc/mc_sys.c:7:
> /home/gavin/dpdk/drivers/bus/fslmc/mc/fsl_mc_sys.h:36: note: this is the
> location of the previous definition  #define dmb() {__asm__ __volatile__("" : :
> : "memory"); }
> 
> cc1: error: unrecognized command line option '-Wno-address-of-packed-
> member' [-Werror]
> cc1: all warnings being treated as errors
> /home/gavin/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target
> 'mc/mc_sys.o' failed
> make[4]: *** [mc/mc_sys.o] Error 1
> 
> Best regards,
> Gavin


  reply	other threads:[~2019-08-01  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 15:34 Gavin Hu (Arm Technology China)
2019-08-01  3:43 ` Hemant Agrawal [this message]
2019-08-26  9:46   ` Gavin Hu (Arm Technology China)

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=VI1PR0401MB25412FABE86E86B50E7359D389DE0@VI1PR0401MB2541.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=Gavin.Hu@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=users@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).