[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <502969FA.6010907@koe-americas.com>
Date: Mon, 13 Aug 2012 20:56:26 +0000
From: David Cullen <David.Cullen@...-americas.com>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Michal Marek <mmarek@...e.cz>,
"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] Fix "/usr/bin/xargs: rm: Argument list too long"
during make distclean
On 8/13/2012 4:38 PM, H. Peter Anvin wrote:
> On 08/13/2012 12:39 PM, David Cullen wrote:
>> When running "make distclean" in a cross chroot environment, the
>> following messages are emitted:
>>
>> [user@...t:/home/work/linux]: make distclean
>> /usr/bin/xargs: rm: Argument list too long
>> make: *** [clean] Error 126
>>
>
> That sounds like a bug in xargs...
>
> -hpa
>
In my specific case, qemu-arm-static calls xargs (In fact, in my
cross chroot, qemu-arm-static is used to run every user mode process).
Do you mean that qemu-arm-static is exposing a latent defect in xargs?
Does qemu-arm-static steal some of the command line space that would
normally be available for xargs? If so, how would xargs figure out
this was happening and handle the problem?
--
Thank you,
David Cullen
Powered by blists - more mailing lists