Dne 13.7.2012 20:30, cody napsal(a):
> Do we have any strict standards for what is and is not portable?
We don't. I only checked the existing userspace code and except for
perf, there is no other usage of getline().
> (I'm aware 'getline' was only added to posix ~4 years ago in 2008).
Ah, good
Do we have any strict standards for what is and is not portable?
(I'm aware 'getline' was only added to posix ~4 years ago in 2008).
--
Cody
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at h
On 11.7.2012 01:47, c...@linux.vnet.ibm.com wrote:
> From: Cody Schafer
>
> For some config options (CONFIG_EXTRA_FIRMWARE, for example), the length
> of a config file line can exceed the 1024 byte buffer.
>
> Switch from fgets to getline to fix.
getline() is not a portable function and kconfig
From: Cody Schafer
For some config options (CONFIG_EXTRA_FIRMWARE, for example), the length
of a config file line can exceed the 1024 byte buffer.
Switch from fgets to getline to fix.
Signed-off-by: Cody Schafer
---
scripts/kconfig/confdata.c |6 --
1 file changed, 4 insertions(+), 2
4 matches
Mail list logo