Here's one I missed before: apparently gzip uses gzip (the system's gzip, not its own just-built binary) in its testsuite. It uses the gzip prog in the PATH to compress a file, then runs tests with zdiff in its source dir. It doesn't seem to make sense to use an external prog instead of its own newly-built binaries for a testsuite, so I'm not sure if this is intentional or a bug in gzip's testsuite.
[EMAIL PROTECTED]:~/gzip-1.3.12$ make check Making check in lib make[1]: Entering directory `/home/chris/gzip-1.3.12/lib' make check-am make[2]: Entering directory `/home/chris/gzip-1.3.12/lib' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/home/chris/gzip-1.3.12/lib' make[1]: Leaving directory `/home/chris/gzip-1.3.12/lib' Making check in doc make[1]: Entering directory `/home/chris/gzip-1.3.12/doc' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/home/chris/gzip-1.3.12/doc' make[1]: Entering directory `/home/chris/gzip-1.3.12' make check-local make[2]: Entering directory `/home/chris/gzip-1.3.12' gzip <gzip.doc >gzip.doc.gz /bin/sh: gzip: command not found make[2]: *** [gzip.doc.gz] Error 127 make[2]: Leaving directory `/home/chris/gzip-1.3.12' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/home/chris/gzip-1.3.12' make: *** [check-recursive] Error 1 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
