On 31/08/2011 18:51, Bruce Dubbs wrote: > I've noticed that there is a spurious file, /t, created in the latest > builds of LFS. The file is 2 bytes long, a 0xff followed by a newline. > > It is a file generated by one of the tests in grep. I'm not sure how to > find which test. It appears to be harmless and the easiest way to > address it is to run: > > rm /t > > after the make check. > > Thoughts?
tests/unibyte-bracket-expr is the culprit (it does `cp $in /t`). Frustratingly a grep for '/t' in the source tree would have found it, but I ended up spotting it by doing `watch -n1 ls /` in another terminal window while the tests were running to find it, thinking the tests were probably too convoluted to spot it through code inspection. I'm not sure why the test does that copy; removing it has no effect - the test still passes. I'll send a patch upstream, but I guess the book could just remove the line prior to running either ./configure or the tests themselves. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
