Re: findutils on interix

On 10/22/2010 03:30 PM, Markus Duft wrote: > Hey :) > [snip] > It seems that max argument length is too high... > > Now, i'm pretty aware that interix is doing _many_ things wrong, and > sysconf(_SC_ARG_MAX) may well return a much too high number, but to > consistently handle such cases, would it

[bug #31420] find --include "*.c" doesn't *.c find files in current directory

Update of bug #31420 (project findutils): Status: Need Info => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #3: And fixed in gre

[bug #31420] find --include "*.c" doesn't *.c find files in current directory

Follow-up Comment #2, bug #31420 (project findutils): Goodness, you are completely right! HEAD DESK! Sorry for the noise ___ Reply to this item at: ___

[bug #31420] find --include "*.c" doesn't *.c find files in current directory

Update of bug #31420 (project findutils): Status:None => Need Info Assigned to:None => jay ___ Follow-up Comment #1: It looks to me a

Re: findutils on interix

On Fri, Oct 22, 2010 at 2:30 PM, Markus Duft wrote: > Hey :) > > I recently updated my findutils builds on interix (work without > any patches (except a gnulib patch i already submitted), thanks > for the great work ;) ), and stumbled across a small problem: > > mduft xargs $ find /usr/ | ./xargs

[bug #31420] find --include "*.c" doesn't *.c find files in current directory

URL: Summary: find --include "*.c" doesn't *.c find files in current directory Project: findutils Submitted by: pcjc2 Submitted on: Fri Oct 22 21:02:09 2010 Category: find

findutils on interix

Hey :) I recently updated my findutils builds on interix (work without any patches (except a gnulib patch i already submitted), thanks for the great work ;) ), and stumbled across a small problem: mduft xargs $ find /usr/ | ./xargs ./xargs: /bin/echo: Cannot allocate memory mduft xargs $ ./xar