From: Mark Wielaard <mark@gnu.wildebeest.org>
To: elfutils-devel@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] configure: Don't use valgrind and sanitize-undefined for make distcheck
Date: Tue, 3 May 2022 01:42:56 +0200 [thread overview]
Message-ID: <1651534976-19190-1-git-send-email-mark@gnu.wildebeest.org> (raw)
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(-)
diff --git a/ChangeLog b/ChangeLog
index 77173d9..f1a14b5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -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.
diff --git a/Makefile.am b/Makefile.am
index 9c47afa..8643312 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:
--
1.8.3.1
reply other threads:[~2022-05-02 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1651534976-19190-1-git-send-email-mark@gnu.wildebeest.org \
--to=mark@gnu.wildebeest.org \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).