On Sat, Apr 27, 2013 at 08:17:36PM +0200, [email protected] wrote:
> From: Luca Barbato <[email protected]>
>
> The suppression file has been originally proposed by Reimar Doeffinger.
> The idea of using set_defaults is from Luca Barbato.
I see no suppression file.
> --- a/configure
> +++ b/configure
> @@ -2221,7 +2225,7 @@ case "$toolchain" in
>
> -set_default arch cc pkg_config sysinclude target_os
> +set_default arch cc pkg_config sysinclude target_os target_exec
order
> @@ -4019,7 +4023,7 @@ HOSTCC_DEPFLAGS=$HOSTCC_DEPFLAGS
> HOSTCC_C=$HOSTCC_C
> HOSTCC_O=$HOSTCC_O
> HOSTLD_O=$HOSTLD_O
> -TARGET_EXEC=$target_exec
> +TARGET_EXEC=$target_exec $target_exec_args
Why not pass the options as part of $target_exec?
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -574,6 +574,18 @@ You can use the command @code{make lcov-reset} to reset
> the coverage
> measurements. You will need to rerun @code{make lcov} after running a
> new test.
>
> +@subsection Using Valgrind
> +
> +The configure script provides a shortcut for using valgrind to spot bugs
Valgrind
> +of the @strong{memcheck} tool of the valgrind suite.
same
> +In case you need finer control over how valgrind is invoked, use the
same
Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
