From: Scott E. <sc...@ju...> - 2014-04-04 12:44:47
|
I don't use the Gumstix repos, but did you explicitly add perf to your image? When I wanted to use perf, I had to add a little kernel patch like this to get around that path problem building perf with Yocto. Could be you could do the fix in the perf recipe, but I was just playing around and this was easy. --- patch --- diff --git git/tools/perf/util/evsel.c-orig git/tools/perf/util/evsel.c index 9f6cebd..d5491f1 100644 --- git/tools/perf/util/evsel.c-orig +++ git/tools/perf/util/evsel.c @@ -15,7 +15,7 @@ #include "cpumap.h" #include "thread_map.h" #include "target.h" -#include "../../include/linux/perf_event.h" +#include "../../../include/linux/perf_event.h" #define FD(e, x, y) (*(int *)xyarray__entry(e->fd, x, y)) #define GROUP_FD(group_fd, cpu) (*(int *)xyarray__entry(group_fd, cpu, 0)) --- patch --- I also needed this set in the kernel config to use it CONFIG_OMAP3_EMU=y CONFIG_HAVE_PERF_EVENTS=y CONFIG_PERF_EVENTS=y CONFIG_HW_PERF_EVENTS=y CONFIG_CPU_HAS_PMU=y -- View this message in context: http://gumstix.8.x6.nabble.com/Issue-with-bitbake-under-Fedora-20-tp4969018p4969019.html Sent from the Gumstix mailing list archive at Nabble.com. |