public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Poselenov <sposelenov@emcraft.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'make headers_check' failed to install headers to arbitrary location
Date: Fri, 15 May 2009 15:30:35 +0400	[thread overview]
Message-ID: <4A0D525B.5070509@emcraft.com> (raw)
In-Reply-To: <200905141854.37869.arnd@arndb.de>

Hello Arnd,

Thanks, but it doesn't help. The same error.

This is actually not a perl error, but the shell's
passing a list of files with added $(install) prefix.

Regards,
Sergei

Arnd Bergmann wrote:
> On Thursday 14 May 2009, Sergei Poselenov wrote:
>>    CHECK   include/linux/tc_ematch (4 files)
>>    CHECK   include/linux/usb (8 files)
>> make[2]: execvp: /bin/sh: Argument list too long
>> make[2]: *** 
> 
> Can you try this patch?
> 
> 	Arnd <><
> 
> --- a/scripts/Makefile.headersinst
> +++ b/scripts/Makefile.headersinst
> @@ -54,8 +54,8 @@ quiet_cmd_remove = REMOVE  $(unwanted)
>        cmd_remove = rm -f $(unwanted-file)
>  
>  quiet_cmd_check = CHECK   $(printdir) ($(words $(all-files)) files)
> -      cmd_check = $(PERL) $< $(INSTALL_HDR_PATH)/include $(SRCARCH) \
> -                  $(addprefix $(install)/, $(all-files));           \
> +      cmd_check = echo $(addprefix $(install)/, $(all-files)) | \
> +		  xargs $(PERL) $< $(INSTALL_HDR_PATH)/include $(SRCARCH) ; \
>  	          touch $@
>  
>  PHONY += __headersinst __headerscheck

  reply	other threads:[~2009-05-15 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 15:42 'make headers_check' failed to install headers to arbitrary location Sergei Poselenov
2009-05-14 16:54 ` Arnd Bergmann
2009-05-15 11:30   ` Sergei Poselenov [this message]
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=4A0D525B.5070509@emcraft.com \
    --to=sposelenov@emcraft.com \
    --cc=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox