summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorBrenda Streiff <brenda.streiff@ni.com>2022-01-29 01:01:28 +0300
committerMasahiro Yamada <masahiroy@kernel.org>2022-02-08 07:20:11 +0300
commit8a4c5b2a6d8ea079fa36034e8167de87ab6f8880 (patch)
treec0915c06ac4a4c3206e41c54d3303374a74cc5e8 /scripts
parentdfd42facf1e4ada021b939b4e19c935dcdd55566 (diff)
downloadlinux-8a4c5b2a6d8ea079fa36034e8167de87ab6f8880.tar.xz
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>
Diffstat (limited to 'scripts')
-rw-r--r--scripts/kconfig/preprocess.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/kconfig/preprocess.c b/scripts/kconfig/preprocess.c
index 0590f86df6e4..748da578b418 100644
--- a/scripts/kconfig/preprocess.c
+++ b/scripts/kconfig/preprocess.c
@@ -141,7 +141,7 @@ static char *do_lineno(int argc, char *argv[])
static char *do_shell(int argc, char *argv[])
{
FILE *p;
- char buf[256];
+ char buf[4096];
char *cmd;
size_t nread;
int i;