[Buildroot] [PATCH] valgrind: install to staging

[Peter Korsgaard]

>>>>> "Arnout" == Arnout Vandecappelle <arnout at mind.be> writes:

Hi,

>> diff --git a/package/valgrind/valgrind.mk b/package/valgrind/valgrind.mk
 >> index cfce8da..f8f205e 100644
 >> --- a/package/valgrind/valgrind.mk
 >> +++ b/package/valgrind/valgrind.mk
 >> @@ -11,6 +11,7 @@ VALGRIND_LICENSE = GPLv2 GFDLv1.2
 >> VALGRIND_LICENSE_FILES = COPYING COPYING.DOCS
 >> VALGRIND_CONF_OPTS = --disable-tls
 >> VALGRIND_AUTORECONF = YES
 >> +VALGRIND_INSTALL_STAGING = YES

 >  I wonder, are there going to be a lot of packages that will autodetect valgrind
 > presence and will now start linking with it?

Do programs need to link against valgrind? I thought it only provided a
header with some magic macros that somehow would direct valgrind to
behave differently, but didn't do anything when not running through
valgrind?

In any case, if the user has enabled valgrind, then he/she presumably
wants to enable valgrind support in all applicable packages, but we
indeed will need to add valgrind as an optional dependency of those.

I don't know how common it is to have explicit valgrind support though,
I guess only a few packages have it.

-- 
Bye, Peter Korsgaard