Thanks John / Tom -- I aim to try that out. Regards, Davis
On Sun, Jul 21, 2013 at 6:58 PM, John Reiser <[email protected]> wrote:
> The top-level Makefile for valgrind looks somewhat ordinary. So you could
> try
> adding "-static -static-libgcc" to to CFLAGS. (Or add "-static" to
> LDFLAGS,
> or add "-Wl,-static" to CFLAGS.) Then look at the final link command:
> invoke
> 'make' and observe the commands that are displayed on stderr. In the worst
> case, then run under "strace -f -o strace.out -e trace=execve make ..."
> then
> inspect strace.out to find the actual process command line. Also look at
> the
> output from ldd, to see how well those attempts worked. You might also
> look
> one level down at memcheck/Makefile, but CFLAGS etc. from the top-level
> Makefile should propagate to the individual tools such as memcheck.
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
