Hi John, Thanks for the reply. I found that perftools-lite do not support static linking (kinda odd). There are no perf.a files to be linked statically with valgrind; however, perftools should work with static linking.
The perftools process is: build your application and retain object files, then use: $pat_build -O apa <executable> This gives a new executable to run. However, I tried instrumenting the nulltool but get: ERROR: Missing required ELF section '.note.link' from the program ../none-amd64-linux I presume this is somehow stripped from none-amd64-linux? Could this line in the makefile have anything to do whit this? 523 # -Wl,--build-id=none is needed when linking tools with a linker that only 524 # knows -Ttext and not -Ttext-segment. Without this flag newer ld versions 525 # (2.20 and later) create a .note.gnu.build-id at the default text segment 526 # address, which of course means the resulting executable 527 # is unusable. So we have to tell ld not to generate that, with 528 # --build-id=none unless the linker supports -Ttext-segment. 529 TOOL_LDFLAGS_COMMON_LINUX = \ 530 -static -nodefaultlibs -nostartfiles -u _start Any ideas? -- View this message in context: http://valgrind.10908.n7.nabble.com/building-valgrind-perftools-lite-linking-error-tp49214p49230.html Sent from the Valgrind - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
