1552 2011-10-03 06:28:39 +0000 Tracing: create separate recipe for perf 2012-07-08 21:44:12 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto unspecified x86 Multiple VERIFIED FIXED (P2)(Scheduled) Low enhancement 1.3 M2 1 richard.purdie bruce.ashfield dvhart jessica.zhang josh laurentiu.serban poky.bs.watcher poky.watcher radu.moisan sgw song.liu --- --- --- oldest_to_newest 16600 0 richard.purdie 2011-10-03 06:28:39 +0000 Perf is currently built as part of the kernel build. If we want to make use of everything perf has to offer we should get rid of the dependency. For example, the kernel build shouldn\'t depend on libnewt, and x32 shouldn\'t have to deal with embedded Python 16756 1 tom.zanussi 2011-10-06 11:44:22 +0000 Perf is currently built as part of the kernel recipe. Perf really wants to use libnewt, libslang, embedded Python, embedded Perl, etc. That ends up in a ridiculous situation where the kernel depends on e.g. libnewt. It also apparently causes problems for x32 enablement. So, making perf a separate recipe seems to make sense. 18218 2 josh 2012-01-18 11:45:50 +0000 perf is also causing issues for non-gplv3 builds since I added binutils to the DEPENDS, see bug #1880. I think the best resolution to bug 1880 is to move perf to a separate recipe in the 1.2 time frame. Thoughts? 18220 3 dvhart 2012-01-18 12:15:11 +0000 It really just comes down to time. If someone else is available with the cycles to come up with a patch, then we're all for getting it done in time for 1.2. 22222 4 bruce.ashfield 2012-06-14 20:27:14 +0000 This is nearly done. Patches are prep'd and will be submitted soon. 22482 5 bruce.ashfield 2012-06-21 22:47:02 +0000 yocto commit: 6b9c19140cd3c75c9862b22febb17af59930d865 22891 6 laurentiu.serban 2012-07-08 21:44:12 +0000 Verified in master revision b0510e547ebcac5548b36df66ad907f7911d33d5