bugfindutils - Bugs: bug #37093, /usr/bin/xargs: rm: Argument list...

 
 

bug #37093: /usr/bin/xargs: rm: Argument list too long during make distclean in cross chroot

Submitter:  None
Submitted:  Tue 14 Aug 2012 12:22:46 PM UTC
 
Category:  xargs Severity:  4 - Important
Item Group:  Wrong result Status:  Need Info
Privacy:  Public Assigned to:  None
Originator Name:  David Cullen Originator Email:  -email is unavailable-
Open/Closed:  Open Release:  None
Fixed Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Sun 01 Sep 2019 08:35:32 AM UTC, comment #5: 

Findutils 4.7.0 was recently released also.   Are you still able to reproduce the problem with it?

James Youngman <jay>
Project Administrator
Sun 08 Dec 2013 09:12:49 PM UTC, comment #4: 

Sorry about the delay in response; are you still able to reproduce this problem?

James Youngman <jay>
Project Administrator
Tue 14 Aug 2012 01:56:55 PM UTC, comment #3: 

> What version of findutils did you experience this problem
> with?


[user@host:/]: xargs --version
xargs (GNU findutils) 4.4.2
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Eric B. Decker, James Youngman, and Kevin Dalley.
Built using GNU gnulib version e5573b1bad88bfabcda181b9e0125fb0c52b7d3b

> What arguments had been passed to configure when it was built?


I don't know.

> What is the output of
>
> xargs --show-limits true < /dev/null


[user@host:/]: xargs --show-limits true < /dev/null
Your environment variables take up 2099 bytes
POSIX upper limit on argument length (this system): 2093005
POSIX smallest allowable upper limit on argument length (all systems): 4096
Maximum length of command we could actually use: 2090906
Size of command buffer we are actually using: 131072

> What is the output of "env | wc" in the environment in which
> xargs is run (i.e. from make - remember that some versions of
> make export a lot of environment variables)?


[user@host:/]: env | wc
     29      33    2097

David Cullen <kerneldeveloper>
Tue 14 Aug 2012 01:36:11 PM UTC, comment #2: 

What version of findutils did you experience this problem with?    What arguments had been passed to configure when it was built?   What is the output of

xargs --show-limits true < /dev/null

What is the output of "env | wc" in the environment in which xargs is run (i.e. from make - remember that some versions of make export a lot of environment variables)?

James Youngman <jay>
Project Administrator
Tue 14 Aug 2012 12:54:00 PM UTC, comment #1: 

A bug report has also been filed on QEMU:

    https://bugs.launchpad.net/qemu/+bug/1036645

David Cullen <kerneldeveloper>
Tue 14 Aug 2012 12:22:46 PM UTC, original submission:  

I am building the Linux kernel in a cross chroot environment.
When I run "make distclean", the following messages are emitted:

    [user@host:/home/work/linux]: make distclean
    /usr/bin/xargs: rm: Argument list too long
    make: *** [clean] Error 126

I create the cross chroot environment by making a copy of the root
file system from an ARM system. I copy qemu-arm-static to /usr/bin
and then chroot into the root file system.

If I modify the make file to pass "-s 122880" to xargs, it fixes
the problem.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jay (Posted a comment)
  • -email is unavailable- added by kerneldeveloper (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-09-01 jay Severity3 - Normal 4 - Important
    2019-09-01 jay StatusNone Need Info

    Back to the top


    Powered by Savane 3.9