From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/2] gcc-8 build fixes
Date: Tue, 3 Apr 2018 10:23:43 +0100 [thread overview]
Message-ID: <8988b191-30cd-a9fe-1cd2-8625c671a7fe@intel.com> (raw)
In-Reply-To: <20180329170531.2478-1-stephen@networkplumber.org>
On 3/29/2018 6:05 PM, Stephen Hemminger wrote:
> This fixes some of the obvious warnings found building DPDK
> with gcc-8. There still are some deeper issues in the rte_hash_table
> code; leave the fix for that up to the maintainer.
>
> Stephen Hemminger (2):
> rte_mbuf: fix strncpy warnings
> rte_metrics: fix strncpy truncation warning
>
> v3
> missing SOB on 1st patch
>
> v2
> fix issues with wrong length in mbuf pool_ops
> don't need memset in metrics names
>
> Stephen Hemminger (2):
> rte_mbuf: fix strncpy warnings
> rte_metrics: fix strncpy truncation warning
I tried with gcc-8 [1] and getting a few more build errors similar to these
ones. Are these two files only build error you get?
[1]
gcc (GCC) 8.0.1 20180401 (experimental)
next prev parent reply other threads:[~2018-04-03 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 17:05 Stephen Hemminger
2018-03-29 17:05 ` [dpdk-dev] [PATCH v3 1/2] rte_mbuf: fix strncpy warnings Stephen Hemminger
2018-04-04 15:35 ` Thomas Monjalon
2018-03-29 17:05 ` [dpdk-dev] [PATCH v3 2/2] rte_metrics: fix strncpy truncation warning Stephen Hemminger
2018-04-04 14:33 ` Thomas Monjalon
2018-04-03 9:23 ` Ferruh Yigit [this message]
2018-04-03 15:10 ` [dpdk-dev] [PATCH v3 0/2] gcc-8 build fixes Stephen Hemminger
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=8988b191-30cd-a9fe-1cd2-8625c671a7fe@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).