summaryrefslogtreecommitdiff
path: root/Makefile.am
diff options
context:
space:
mode:
authorMark Wielaard <mark@klomp.org>2022-05-03 01:35:53 +0200
committerMark Wielaard <mark@klomp.org>2022-05-03 01:35:53 +0200
commit6d0c3b57429add5b6494259c1c06499e52cff4d5 (patch)
treea930afc8553ed35bdedb12d128df2b05e7214dfb /Makefile.am
parent059e690e896e37c16774047bd1fd0c9e608545b8 (diff)
downloadelfutils-6d0c3b57429add5b6494259c1c06499e52cff4d5.tar.gz
configure: Don't use valgrind and sanitize-undefined for make distcheck
make distcheck would always run with --enable-valgrind and --enable-sanitize-undefined. Assuming the maintainer would run this just before doing a release. But this makes distcheck really, really, really slow. And we have various buildbots now that run various combinations of valgrind, undefined and/or address sanitizer over every commit now. This make make distcheck "fast" again. Signed-off-by: Mark Wielaard <mark@klomp.org>
Diffstat (limited to 'Makefile.am')
-rw-r--r--Makefile.am1
1 files changed, 0 insertions, 1 deletions
diff --git a/Makefile.am b/Makefile.am
index 9c47afa9..8643312a 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -38,7 +38,6 @@ EXTRA_DIST = elfutils.spec GPG-KEY NOTES CONTRIBUTING \
# Run all tests under valgrind.
AM_DISTCHECK_CONFIGURE_FLAGS = \
--libdir=`echo $(libdir) | sed "s,^$(exec_prefix),$$dc_install_base,"`\
- --enable-valgrind --enable-sanitize-undefined \
CC="$(CC)"
distcheck-hook: