All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: nicolas.dichtel@6wind.com, Sam Ravnborg <sam@ravnborg.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: make headers_install fail when path is too long
Date: Thu, 07 Mar 2013 09:26:09 +0100	[thread overview]
Message-ID: <51384F21.9070800@suse.cz> (raw)
In-Reply-To: <51376E6C.4040903@6wind.com>

Dne 6.3.2013 17:27, Nicolas Dichtel napsal(a):
> -        $(PERL) $< $(installdir) $(SRCARCH) $(input-files); \
[...]
> +    @echo $(input-files) > $(INSTALL_HDR_PATH)/.input-files

Are you sure this is a reliable fix? What make does is to spawn

/bin/sh -c 'echo <long list of files> > usr/include/.input-files'

here. So I guess that it works for you just because "sh -c" is shorter
than "sh -c 'perl scripts/headers_install.pl...'".

Michal

  parent reply	other threads:[~2013-03-07  8:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 11:16 make headers_install fail when path is too long Nicolas Dichtel
2013-03-06 16:10 ` 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 [this message]
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=51384F21.9070800@suse.cz \
    --to=mmarek@suse.cz \
    --cc=bruce.ashfield@windriver.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=sam@ravnborg.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.