On 6/28/07, Eric Blake-1 <[EMAIL PROTECTED]> wrote:
Several GNU projects allow './configure; make check', whereas findutils
currently requires './configure; make; make check'. OK to apply to
branch and head? As for an argument for inclusion on the branch,
this change is minimal, and does not change any code, just the order
in which make traverses directories.
2007-06-28 Eric Blake <[EMAIL PROTECTED]>
Allow 'make check' to work without prior 'make all'.
* find/Makefile.am (SUBDIRS): Build in . before testsuite.
* locate/Makefile.am (SUBDIRS): Likewise.
* xargs/Makefile.am (SUBDIRS): Likewise.
diff -u -p -r1.9 Makefile.am
--- find/Makefile.am 3 Jul 2005 16:07:08 -0000 1.9
+++ find/Makefile.am 28 Jun 2007 14:48:48 -0000
@@ -8,7 +8,7 @@ EXTRA_DIST = defs.h $(man_MANS)
INCLUDES = -I../gnulib/lib -I$(top_srcdir)/lib -I$(top_srcdir)/gnulib/lib
-I../intl -DLOCALEDIR=\"$(localedir)\"
LDADD = ../lib/libfind.a ../gnulib/lib/libgnulib.a @INTLLIBS@
man_MANS = find.1
-SUBDIRS = testsuite
+SUBDIRS = . testsuite
Is this really the only way to control findutils' directory traversal order?
James.
_______________________________________________
Findutils-patches mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/findutils-patches