From: Stephen Hemminger <stephen@networkplumber.org>
To: "Tran (US), Katherine K" <katherine.k.tran@boeing.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Redundant struct ether_addr
Date: Wed, 25 Sep 2019 13:22:10 -0700 [thread overview]
Message-ID: <20190925132210.7725e6e0@hermes.lan> (raw)
In-Reply-To: <5cd0d1d8b5bd483692c0e3d4d5463c16@boeing.com>
On Wed, 25 Sep 2019 20:06:43 +0000
"Tran (US), Katherine K" <katherine.k.tran@boeing.com> wrote:
> Hello,
>
> I am running into an issue of a redundant struct name. Apparently, 'struct ether_addr' is redefined in DPDK (rte_ether.h). The previous definition of ether_addr is from one of the included core network API files (netinet/if_ether.h).
>
> How should I proceed with this compile error? Shouldn't DPDK have its own userspace?
>
> Regards,
> Katherine
Already fixed in 19.08.
With earlier versions of DPDK, it is possible to cross headers since the binary layout
is the same but it requires lots of unnecessary pain.
next prev parent reply other threads:[~2019-09-25 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 20:06 Tran (US), Katherine K
2019-09-25 20:22 ` Stephen Hemminger [this message]
2019-09-25 20:31 ` Tran (US), Katherine K
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=20190925132210.7725e6e0@hermes.lan \
--to=stephen@networkplumber.org \
--cc=katherine.k.tran@boeing.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).