summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2018-05-13 22:28:24 +0200
committerLennart Poettering <lennart@poettering.net>2018-05-17 09:54:36 -0700
commitd18cb3937bdc2efede153abce1cd8ddae941d762 (patch)
treefc85b7d3dcfea9ea6261b79d56bda058b1f76d5e /README
parent51b66c7a8a8afc8241373e864514d5ac7b87f169 (diff)
downloadsystemd-d18cb3937bdc2efede153abce1cd8ddae941d762.tar.gz
Turn VALGRIND variable into a meson configuration switch
Configuration through environment variable is inconvenient with meson, because they cannot be convieniently changed and/or are not preserved during reconfiguration (https://github.com/mesonbuild/meson/issues/1503). This adds -Dvalgrind=true/false, which has the advantage that it can be set at any time with meson configure -Dvalgrind=... and ninja will rebuild targets as necessary. Additional minor advantages are better consistency with the options for hashmap debugging, and typo avoidance with '#if' instead of '#ifdef'.
Diffstat (limited to 'README')
-rw-r--r--README13
1 files changed, 6 insertions, 7 deletions
diff --git a/README b/README
index d18eb7dc1e..2cde08c37e 100644
--- a/README
+++ b/README
@@ -303,13 +303,12 @@ WARNINGS:
For more information on this issue consult
https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
- To run systemd under valgrind, compile with VALGRIND defined
- (e.g. CPPFLAGS='... -DVALGRIND=1' meson <options>) and have valgrind
- development headers installed (i.e. valgrind-devel or
- equivalent). Otherwise, false positives will be triggered by code which
- violates some rules but is actually safe. Note that valgrind generates
- nice output only on exit(), hence on shutdown we don't execve()
- systemd-shutdown.
+ To run systemd under valgrind, compile with meson option
+ -Dvalgrind=true and have valgrind development headers installed
+ (i.e. valgrind-devel or equivalent). Otherwise, false positives will be
+ triggered by code which violates some rules but is actually safe. Note
+ that valgrind generates nice output only on exit(), hence on shutdown
+ we don't execve() systemd-shutdown.
STABLE BRANCHES AND BACKPORTS