From: Wolfgang Denk <wd@denx.de>
To: Sergei Poselenov <sposelenov@emcraft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: 'make headers_check' failed to install headers to arbitrary location
Date: Thu, 04 Jun 2009 19:07:15 +0200 [thread overview]
Message-ID: <20090604170715.98806832E416@gemini.denx.de> (raw)
In-Reply-To: <20090604175536.2a1d0add@emcraft.com>
Dear Sergei,
In message <20090604175536.2a1d0add@emcraft.com> you wrote:
>
> Here is another version of the patch which fixes
> the "Argument list too long" error for "make headers_check", used xargs
> to minimize the perl calls (thanks, Wolfgang).
Hm... but now we have a useless use of cat and a temp file.
> - cmd_check = $(PERL) $< $(INSTALL_HDR_PATH)/include $(SRCARCH) \
> - $(addprefix $(install)/, $(all-files)); \
> +# Headers list can be pretty long, xargs helps to avoid
> +# the "Argument list too long" error.
> + cmd_check = rm -f hdrlist; touch hdrlist; \
> + for f in $(all-files); do \
> + echo "$(install)/$${f} " >> hdrlist; done; \
> + cat hdrlist | xargs \
> + $(PERL) $< $(INSTALL_HDR_PATH)/include $(SRCARCH); \
> + rm -f hdrlist; \
Why not simply:
for f in $(all-files); do
echo "$(install)/$${f}"
done | xargs $(PERL) ...
?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A witty saying proves nothing, but saying something pointless gets
people's attention.
next prev parent reply other threads:[~2009-06-04 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 15:42 Sergei Poselenov
2009-05-14 16:54 ` 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 [this message]
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=20090604170715.98806832E416@gemini.denx.de \
--to=wd@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sposelenov@emcraft.com \
/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
all inboxes | Powered by JetHome®