kconfig: let 'shell' return enough output for deep path names
authorBrenda Streiff <brenda.streiff@ni.com>
Fri, 28 Jan 2022 22:01:28 +0000 (16:01 -0600)
committerMasahiro Yamada <masahiroy@kernel.org>
Tue, 8 Feb 2022 04:20:11 +0000 (13:20 +0900)
commit8a4c5b2a6d8ea079fa36034e8167de87ab6f8880
treec0915c06ac4a4c3206e41c54d3303374a74cc5e8
parentdfd42facf1e4ada021b939b4e19c935dcdd55566
kconfig: let 'shell' return enough output for deep path names

The 'shell' built-in only returns the first 256 bytes of the command's
output. In some cases, 'shell' is used to return a path; by bumping up
the buffer size to 4096 this lets us capture up to PATH_MAX.

The specific case where I ran into this was due to commit 1e860048c53e
("gcc-plugins: simplify GCC plugin-dev capability test"). After this
change, we now use `$(shell,$(CC) -print-file-name=plugin)` to return
a path; if the gcc path is particularly long, then the path ends up
truncated at the 256 byte mark, which makes the HAVE_GCC_PLUGINS
depends test always fail.

Signed-off-by: Brenda Streiff <brenda.streiff@ni.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
scripts/kconfig/preprocess.c