Paul Eggert <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: > >> You can work around the problem by removing all of the >> *-tests files from your checked-out directory: >> >> rm `find tests -name '*-tests'` >> >> I've removed those (generated) files from CVS, >> so they shouldn't cause any more trouble. > > I was about to report the same problem (after suffering from it for a > few months -- I never got around to reporting it but somehow it bugged > me this morning, what a coincidence!). It appears that your fix of > removing *-tests from CVS has not been pushed out to me,
I've just run rsync. > but I just > wanted to mention (in case you didn't notice already) a couple of things: > > 1. The file src/du-tests looks out of place. It was good enough for my purpose, but it's not portable and not even reliable on my development system. I used it while revamping du to help ensure that my changes didn't have unwanted side effects. I suppose it belongs in tests/du/. > 2. The files tests/ls/ls-tests and tests/tr/range-tests are not > removed by "make maintainer-clean"; is this intentional? I didn't > remove them in my copy, as it wasn't necessary to remove them to fix > the "make check" problem. Those files deserved to be removed :-) ls/ls-tests was once generated, but hasn't been used for a long time tr/range-tests contained testing notes from 10 years ago. _______________________________________________ Bug-coreutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-coreutils
