Follow-up Comment #8, bug #64171 (project findutils):
I also just tried with the following ./configure options and it didn't help.
Still got the same results.
./configure --disable-leaf-optimisation --disable-d_type-optimization
--disable-largefile --disable-year2038 --disable-threads --without
Follow-up Comment #7, bug #64171 (project findutils):
Seems like my last comment got lost.
I do see the same behavior if I build it myself. If I run with -D all and
without any -maxdepth arg (the scenario that fails), the ./opt folder does not
appear anywhere in the output.
If I run with -D all
Follow-up Comment #6, bug #64171 (project findutils):
> Rick, can you reproduce this issue with findutils built from source code?
I'm pretty sure I tried that and the answer is yes I can reproduce it. But I
will double check this afternoon.
I will also gather the log without -maxdepth, but I t
Follow-up Comment #4, bug #64171 (project findutils):
[comment #2 comment #2:]
> What do you see if you turn on debug output? For example,
> ...
I attached the output of "sudo gfind -D all / -maxdepth 2" as debug.log.
Remember that this command actually works. It works fine at least as far as
Follow-up Comment #1, bug #64171 (project findutils):
I forgot to mention that it finds everything in /opt (afaict) if I do the
search directly on /opt.
> cd /
> sudo gfind opt > ~/files.txt
I see all the files I expect to in ~/files.txt.
___
ity: 3 - Normal
Item Group: Wrong result
Status: None
Privacy: Public
Assigned to: None
Originator Name: Rick Kilgore
Originator Email:
Open/Closed: Open
Release: 4.9.0
Discussion Loc
