[COMMITTED] configure: Don't use valgrind and sanitize-undefined for make distcheck
Commit Message
From: Mark Wielaard <mark@klomp.org>
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>
---
ChangeLog | 5 +++++
Makefile.am | 1 -
2 files changed, 5 insertions(+), 1 deletion(-)
@@ -1,3 +1,8 @@
+2022-05-02 Mark Wielaard <mark@klomp.org>
+
+ * Makefile.am (AM_DISTCHECK_CONFIGURE_FLAGS): Remove
+ --enable-valgrind --enable-sanitize-undefined.
+
2022-04-25 Mark Wielaard <mark@klomp.org>
* configure.ac (AC_INIT): Set version to 0.187.
@@ -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: