Don't build the kadm5/unit-test test programs during "make all"; build

them during "make check" via test dependencies for consistency with
the way we handle other test programs.  (Also means we don't need
libraries to be linkable until later in the build process.)

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@22404 dc483132-0cff-0310-8789-dd5450dbe970

diff --git a/src/lib/kadm5/unit-test/Makefile.in b/src/lib/kadm5/unit-test/Makefile.in
index f7f7fd85fee113d2a7bdf42124cab5a3013128f2..91729d7d93a25b78db13170c24658833e35c3b40 100644 (file)
--- a/src/lib/kadm5/unit-test/Makefile.in
+++ b/src/lib/kadm5/unit-test/Makefile.in
@@ -11,10 +11,6 @@ DEFS=
 SRCS= init-test.c destroy-test.c handle-test.c iter-test.c setkey-test.c \
        randkey-test.c lock-test.c
 
-all:: init-test destroy-test client-handle-test client-iter-test
-all:: randkey-test server-handle-test lock-test server-iter-test 
-all:: server-setkey-test client-setkey-test
-
 #
 # The client-side test programs.
 #