| Summary: | Tracing: perf trace scripting support | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Richard Purdie <richard.purdie> |
| Component: | meta-yocto | Assignee: | Tom Zanussi <tom.zanussi> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | alexandrux.palalau, dvhart, jessica.zhang, poky.bs.watcher, poky.watcher, song.liu |
| Version: | unspecified | ||
| Target Milestone: | 1.3 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Richard Purdie
2011-10-03 06:29:33 UTC
The problem I had previously was enabling the Perl and Python bindings. The perf Makefile expects the output of the target's python-config –cflags and –ldflags invocation e.g.: python-config --cflags –ldflags: -I/usr/include/python2.6 -I/usr/include/python2.6 -fno-strict-aliasing -DNDEBUG python-config –ldflags: -L/usr/lib/python2.6/config -lpthread -ldl -lutil -lm -lpython2.6 Similarly for Perl e.g. we need the output of perl -MExtUtils::Embed -e ccopts run on the target. Obviously we can't run it on the target during build-time, so I need to figure how to get the same thing at build time. python-config should be manipulated by our binconfig.bbclass to provide the right values. The perl situation is more tricky... Moving to post 1.2, but will try and bring it in if possible. Implemented and pulled into poky/master and the linux-yocto 3.0/3.2/3.4 kernels. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2dac207e392cd9d94a0812d9bba350e1d8c322eb Verified on master branch, commit ID 83448c4b318ce60a54aae24a9a247456fa94caaf |