busybox/testsuite/ls/ls-h-works

# FEATURE: CONFIG_FEATURE_LS_SORTFILES CONFIG_FEATURE_HUMAN_READABLE

[ -n "$d" ] || d=..
LC_ALL=C ls -h "$d" > logfile.gnu
LC_ALL=C busybox ls -h "$d" > logfile.bb
diff -ubw logfile.gnu logfile.bb
randomtest fixes Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com> 2010-05-11 07:23:57 +05:30			`# FEATURE: CONFIG_FEATURE_LS_SORTFILES CONFIG_FEATURE_HUMAN_READABLE`

egor duda writes: Hi! I've created a patch to busybox' build system to allow building it in separate tree in a manner similar to kbuild from kernel version 2.6. That is, one runs command like 'make O=/build/some/where/for/specific/target/and/options' and everything is built in this exact directory, provided that it exists. I understand that applyingc such invasive changes during 'release candidates' stage of development is at best unwise. So, i'm currently asking for comments about this patch, starting from whether such thing is needed at all to whether it coded properly. 'make check' should work now, and one make creates Makefile in build directory, so one can run 'make' in build directory after that. One possible caveat is that if we build in some directory other than source one, the source directory should be 'distclean'ed first. egor 2004-10-08 13:16:08 +05:30			`[ -n "$d" ] \|\| d=..`
ls: fix --color handling. Closes bug 435. Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com> 2009-07-02 17:55:51 +05:30			`LC_ALL=C ls -h "$d" > logfile.gnu`
			`LC_ALL=C busybox ls -h "$d" > logfile.bb`
			`diff -ubw logfile.gnu logfile.bb`