From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Michal Marek <mmarek@suse.cz>, linux-kbuild@vger.kernel.org
Subject: make headers_install fail when path is too long
Date: Wed, 06 Mar 2013 12:16:33 +0100 [thread overview]
Message-ID: <51372591.1090606@6wind.com> (raw)
This problem has probably already been reported, but I don't find the fix in a
kernel.org tree and I don't understand why.
Here is the problem:
root@schnaps:/home/rbb/averyveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryveryverylongpath/linux(master)>make
headers_install INSTALL_HDR_PATH=/tmp/tmp/
CHK include/generated/uapi/linux/version.h
make[1]: Nothing to be done for `all'.
make[1]: Nothing to be done for `relocs'.
make[2]: execvp: /bin/sh: Argument list too long
make[2]: *** [/tmp/tmp//include/linux/.install] Error 127
make[1]: *** [linux] Error 2
make: *** [headers_install] Error 2
I see that this problem has been reported several times on the web, but I do not
find why it's not fixed upstream.
Some patches are available:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=53cc748b93e8af584557d6db5309c3e955182c5c
Any comment/suggestion is welcome.
Regards,
Nicolas
next reply other threads:[~2013-03-06 11:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:16 Nicolas Dichtel [this message]
2013-03-06 16:10 ` make headers_install fail when path is too long Sam Ravnborg
2013-03-06 16:24 ` Michal Marek
2013-03-06 16:27 ` Nicolas Dichtel
2013-03-06 16:50 ` Bruce Ashfield
2013-03-07 8:26 ` Michal Marek
2013-03-07 13:28 ` Bruce Ashfield
2013-04-26 16:36 ` [PATCH] fix make headers_install " Nicolas Dichtel
2013-04-26 18:14 ` Bruce Ashfield
2013-04-26 18:57 ` Sam Ravnborg
2013-04-29 12:13 ` Michal Marek
2013-04-29 12:17 ` Nicolas Dichtel
2013-04-29 12:15 ` [PATCH linux-next v2] " Nicolas Dichtel
2013-04-29 12:34 ` Bruce Ashfield
2013-05-06 8:19 ` Nicolas Dichtel
2013-05-17 9:12 ` Nicolas Dichtel
2013-05-17 20:08 ` Michal Marek
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=51372591.1090606@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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.