summaryrefslogtreecommitdiff
path: root/Makefile.in
diff options
context:
space:
mode:
authorWaldemar Brodkorb <wbx@uclibc-ng.org>2016-10-28 20:29:21 +0200
committerWaldemar Brodkorb <wbx@uclibc-ng.org>2016-10-28 20:31:55 +0200
commit99ef2719fb3d703fe38c4113cd7f5adec516dd3a (patch)
tree2c1f77cb41b60ccbf8faa77a3640491a3546b546 /Makefile.in
parent543308f6c46cf2edf8a524bc9c631e472570fe72 (diff)
test: remove test suite
The test suite is now a developed in a separate git repository. See here: http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng-test.git The test suite should be just like every other software compiled with the cross-toolchain. In the past strange problems where found when the test suite got build in the toolchain creation step.
Diffstat (limited to 'Makefile.in')
-rw-r--r--Makefile.in13
1 files changed, 0 insertions, 13 deletions
diff --git a/Makefile.in b/Makefile.in
index 877a0b69d..76008a2a6 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -539,7 +539,6 @@ include_clean:
clean: include_clean
$(Q)$(RM) -r $(top_builddir)lib
@$(MAKE) -C utils CLEAN_utils
- +$(MAKE) -s -C test clean
$(Q)$(RM) $(top_builddir)extra/scripts/unifdef
$(Q)$(RM) -r $(LOCAL_INSTALL_PATH)
@@ -556,15 +555,3 @@ dist release:
cat ../uClibc-$(VERSION).tar | bzip2 -c9 > ../uClibc-$(VERSION).tar.bz2
cat ../uClibc-$(VERSION).tar | xz -e -c8 > ../uClibc-$(VERSION).tar.xz
du -b ../uClibc-$(VERSION).tar.{bz2,xz}
-
-test check: test_compile
- $(Q)$(MAKE) -C test \
- $(if $(O),top_builddir=$(O)/)
-
-test_compile: $(LOCAL_INSTALL_PATH)
- $(Q)$(MAKE) -C test compile \
- $(if $(O),top_builddir=$(O)/)
-
-test_gen: $(LOCAL_INSTALL_PATH)
- $(Q)$(MAKE) -C test gen \
- $(if $(O),top_builddir=$(O)/)