Re: [dpdk-dev] [PATCH] config: remove insecure warnings

2016-12-07 Thread Thomas Monjalon
2016-12-05 10:27, Bruce Richardson: > On Sun, Dec 04, 2016 at 11:17:06PM +0100, Thomas Monjalon wrote: > > There was an option CONFIG_RTE_INSECURE_FUNCTION_WARNING (disabled by > > default), which prevents from using some libc functions: > > sprintf, snprintf, vsnprintf, strcpy, strncpy, strcat, st

Re: [dpdk-dev] [PATCH] config: remove insecure warnings

2016-12-06 Thread Stephen Hemminger
On Sun, 4 Dec 2016 23:17:06 +0100 Thomas Monjalon wrote: > There was an option CONFIG_RTE_INSECURE_FUNCTION_WARNING (disabled by > default), which prevents from using some libc functions: > sprintf, snprintf, vsnprintf, strcpy, strncpy, strcat, strncat, sscanf, > strtok, strsep and strlen. > >

Re: [dpdk-dev] [PATCH] config: remove insecure warnings

2016-12-05 Thread Bruce Richardson
On Sun, Dec 04, 2016 at 11:17:06PM +0100, Thomas Monjalon wrote: > There was an option CONFIG_RTE_INSECURE_FUNCTION_WARNING (disabled by > default), which prevents from using some libc functions: > sprintf, snprintf, vsnprintf, strcpy, strncpy, strcat, strncat, sscanf, > strtok, strsep and strlen.

[dpdk-dev] [PATCH] config: remove insecure warnings

2016-12-04 Thread Thomas Monjalon
There was an option CONFIG_RTE_INSECURE_FUNCTION_WARNING (disabled by default), which prevents from using some libc functions: sprintf, snprintf, vsnprintf, strcpy, strncpy, strcat, strncat, sscanf, strtok, strsep and strlen. It's all about using them at the right place with the right precautions.