public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Cullen <David.Cullen@koe-americas.com>
To: Michal Marek <mmarek@suse.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] ARM Fix /usr/bin/xargs: etags: Argument list too long
Date: Wed, 8 Aug 2012 15:59:43 +0000	[thread overview]
Message-ID: <50228CEF.2050208@koe-americas.com> (raw)
In-Reply-To: <50227AB0.6010301@suse.cz>

On 8/8/2012 10:41 AM, Michal Marek wrote:
> Dne 8.8.2012 16:32, David Cullen napsal(a):
>> 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.
> 
> This looks like a bug in xargs, it should make sure that the commandline
> fits into ARG_MAX.

Actually, it appears to be caused by the combination of
qemu-arm-static and xargs. When I run "make ARCH=arm TAGS" on an ARM
target, I do not see the problem.

> BTW, a better workaround would be to use the -s option, which
> limits the size of the argument list.

That works.

I'll submit another RFC patch.

-- 
Thank you,
David Cullen

      reply	other threads:[~2012-08-08 15:59 UTC|newest]

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

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=50228CEF.2050208@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