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.
Found it. The test is unibyte-bracket-expr
. "${srcdir=.}/init.sh"; path_prepend_ ../src
require_ru_RU_koi8_r
LC_ALL=ru_RU.KOI8-R
export LC_ALL
fail=0
for i in 8 9 a b c d e f; do
for j in 0 1 2 3 4 5 6 7 8 9 a b c d e f; do
in=in-$i$j
b=$(printf "\\x$i$j")
echo "$b" > $in || framework_failure_
cp $in /t
grep "[$b]" $in > out || fail=1
compare out $in || fail=1
done
done
Exit $fail
Commenting out the line 'cp $in /t' does not seem to affect the test.
The question now is whether to do
sed -i 's:\(cp $in /t\):#\1:' tests/unibyte-bracket-expr
Or just delete the /t file that's created.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
