public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Cullen <David.Cullen@koe-americas.com>
To: "mmarek@suse.cz" <mmarek@suse.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH] ARM Fix /usr/bin/xargs: etags: Argument list too long
Date: Wed, 8 Aug 2012 14:32:51 +0000	[thread overview]
Message-ID: <50227893.7070600@koe-americas.com> (raw)

Patch applies to

    commit 42a579a0f960081cd16fc945036e4780c3ad3202

When running "make ARCH=arm TAGS" in a chroot using qemu-arm-static,
the following message is emitted:

    [user@host:/home/work/linux]: make ARCH=arm TAGS
      GEN     TAGS
    /usr/bin/xargs: etags: Argument list too long

This can be fixed by by passing "-L 1024" to xargs in scripts/tags.sh.

The "1024" was a guess. A value of "3862" changes the message to

    /usr/bin/xargs: argument list too long

Using "2048" also fixes the problem. However, I don't know how much
headroom that leaves

Does anyone know why the argument lists must be shorter for ARM? All
of the documentation I have available says that 4096 should be the
limit.

Signed-off-by: David Cullen <david.cullen@koe-americas.com>
---
 scripts/tags.sh |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/tags.sh b/scripts/tags.sh
index cff8faa..7f4ebb3 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -121,7 +121,7 @@ dogtags()

 exuberant()
 {
-       all_sources | xargs $1 -a                               \
+       all_sources | xargs -L 1024 $1 -a                       \
        -I __initdata,__exitdata,__acquires,__releases          \
        -I __read_mostly,____cacheline_aligned                  \
        -I ____cacheline_aligned_in_smp                         \
--
1.7.9.5

             reply	other threads:[~2012-08-08 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 14:32 David Cullen [this message]
2012-08-08 14:41 ` [RFC PATCH] ARM Fix /usr/bin/xargs: etags: Argument list too long Michal Marek
2012-08-08 15:59   ` David Cullen

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=50227893.7070600@koe-americas.com \
    --to=david.cullen@koe-americas.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox