On 08/16/2018 06:07 PM, He Zhe wrote:
> 
> 
> On 2018年08月16日 15:59, Anuj Mittal wrote:
>> On 08/14/2018 04:09 PM, [email protected] wrote:
>>> From: He Zhe <[email protected]>
>>>
>>> And add strncpy warning/error fixes for GCC8
>>>
>>> Signed-off-by: He Zhe <[email protected]>
>>> ---
>>>  .../dpdk-17.11-Fix-strncpy-error-for-GCC8.patch    | 82 
>>> ++++++++++++++++++++++
>>>  .../dpdk/{dpdk_17.11.1.bb => dpdk_17.11.3.bb}      |  4 +-
>>>  2 files changed, 85 insertions(+), 1 deletion(-)
>>>  create mode 100644 
>>> recipes-extended/dpdk/dpdk/dpdk-17.11-Fix-strncpy-error-for-GCC8.patch
>>>  rename recipes-extended/dpdk/{dpdk_17.11.1.bb => dpdk_17.11.3.bb} (66%)
>>>
>>> diff --git 
>>> a/recipes-extended/dpdk/dpdk/dpdk-17.11-Fix-strncpy-error-for-GCC8.patch 
>>> b/recipes-extended/dpdk/dpdk/dpdk-17.11-Fix-strncpy-error-for-GCC8.patch
>>> new file mode 100644
>>> index 0000000..2014b3e
>>> --- /dev/null
>>> +++ b/recipes-extended/dpdk/dpdk/dpdk-17.11-Fix-strncpy-error-for-GCC8.patch
>>> @@ -0,0 +1,82 @@
>>> +From 30234e8bf0a8c0fe348aaa147307488f59b3265a Mon Sep 17 00:00:00 2001
>>> +From: He Zhe <[email protected]>
>>> +Date: Mon, 13 Aug 2018 20:06:31 +0800
>>> +Subject: [PATCH] dpdk 17.11: Fix strncpy error for GCC8
>>> +
>>> +GCC 8 adds -Wstringop-truncation. If -Werror=stringop-truncation is
>>> +enabled. We will meet errors like the following:
>>> +
>>> +examples/vhost_scsi/scsi.c:213:4: error: 'strncpy' output may be truncated
>>> +copying 32 bytes from a string of length 63 [-Werror=stringop-truncation]
>>> +|     strncpy((char *)vpage->params, bdev->name, 32);
>>> +|     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> +
>>> +Upstream-Status: Submitted [[email protected]]
>>> +
>> For some reason, I can't find this patch on the stable mailing list. Can
>> you please include the link to archive?
> 
> My mail was blocked there since it's member only. I just resent it and It's 
> there now.
> 

Thanks, I have pushed this now. Sorry for the delay.

Thanks,

Anuj
-- 
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel

Reply via email to