On 2011-09-07 13:22:09 +0200, Simon Josefsson wrote:
> Vincent, Bruno, if you can think of ways of making the situation better
> even for projects that use libtool wrappers of self-tests, then let's do
> that too -- I'm just mentioning that -no-install may be a solution.
Yes, I think this should b
Another solution is to put
AM_LDFLAGS = -no-install
in the Makefile.am of your self-test directory, so libtool will not
build wrappers for them.
I have not seen any negative effects of doing this, and it helps
significantly with issues like this (especially for running gdb).
Vincent, Bruno, if
Hi Vincent,
> valgrind-tests.texi says:
>
> However, this means that binaries invoked through scripts will not be
> invoked under valgrind, which could be solved by adding the following:
>
> @smallexample
> TESTS_ENVIRONMENT = VALGRIND='$(VALGRIND)'
> @end smallexample
>
> And then modify the s
Hi,
I've just done a test with the GNU MPC trunk, which is now based
on valgrind-tests.m4, and this is not compatible with libtool,
because it generates wrapper scripts.
valgrind-tests.texi says:
However, this means that binaries invoked through scripts will not be
invoked under valgrind, which
