From: Sergei Poselenov <sposelenov@emcraft.com>
To: linux-kernel@vger.kernel.org
Subject: 'make headers_check' failed to install headers to arbitrary location
Date: Thu, 14 May 2009 19:42:51 +0400 [thread overview]
Message-ID: <4A0C3BFB.1010305@emcraft.com> (raw)
Hello,
I'm trying to install kernel headers to build a cross-toolchain, but got
the following:
make ARCH=arm
INSTALL_HDR_PATH=/work/psl/eldk-builds/arm-2009-04-21/work/var/tmp/crosstool-0.43-3-root/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/arm-linux-gnueabi/arm-linux-gnueabi/
headers_check
...
CHECK include/linux/raid (2 files)
CHECK include/linux/spi (1 files)
CHECK include/linux/sunrpc (1 files)
CHECK include/linux/tc_act (6 files)
CHECK include/linux/tc_ematch (4 files)
CHECK include/linux/usb (8 files)
make[2]: execvp: /bin/sh: Argument list too long
make[2]: ***
[/work/psl/eldk-builds/arm-2009-04-21/work/var/tmp/crosstool-0.43-3-root/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/arm-linux-gnueabi/arm-linux-gnueabi//include/linux/.check]
Error 127
make[1]: *** [linux] Error 2
make: *** [headers_check] Error 2
->
The kernel version is 2.6.28
However, this works fine for 2.6.24.2
Running make with '-n', I've found the problem is that the filelist
passed as argument to scripts/headers_check.pl apparently is too big.
The error depends also on a bash version, it failed on 2.05a, but passed
on 3.2.39. Unfortunately, bash (or the hole host system) upgrade is not
an option. Also, I'm sure I could find a path length big enough to
reproduce the error on a modern bash.
What would you suggest to resolve the problem?
Thanks for any help.
Regards,
Sergei
next reply other threads:[~2009-05-14 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 15:42 Sergei Poselenov [this message]
2009-05-14 16:54 ` 'make headers_check' failed to install headers to arbitrary location Arnd Bergmann
2009-05-15 11:30 ` Sergei Poselenov
2009-05-21 13:46 ` [PATCH] " Sergei Poselenov
2009-06-04 13:55 ` Sergei Poselenov
2009-06-04 17:07 ` Wolfgang Denk
2009-06-05 12:11 ` Sergei Poselenov
2009-06-05 23:01 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0C3BFB.1010305@emcraft.com \
--to=sposelenov@emcraft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.