Re: [OE-core] oprofile rebuilds for different MACHINES (sstate)

2015-09-09 Thread Denys Dmytriyenko
On Tue, Aug 11, 2015 at 09:35:42PM -0700, Khem Raj wrote: > > > On Aug 11, 2015, at 8:26 PM, Denys Dmytriyenko wrote: > > > > So, I've been debugging the issue of oprofile rebuilding from one MACHINE to > > another (causing PR issues, etc). I was able to trace it down to this line: > > > > EXTR

Re: [OE-core] oprofile rebuilds for different MACHINES (sstate)

2015-08-11 Thread Philip Balister
On 08/12/2015 05:26 AM, Denys Dmytriyenko wrote: > So, I've been debugging the issue of oprofile rebuilding from one MACHINE to > another (causing PR issues, etc). I was able to trace it down to this line: Why not use perf instead of oprofile? Philip > > EXTRA_OECONF = "--with-kernel=${STAGING

Re: [OE-core] oprofile rebuilds for different MACHINES (sstate)

2015-08-11 Thread Khem Raj
> On Aug 11, 2015, at 8:26 PM, Denys Dmytriyenko wrote: > > So, I've been debugging the issue of oprofile rebuilding from one MACHINE to > another (causing PR issues, etc). I was able to trace it down to this line: > > EXTRA_OECONF = "--with-kernel=${STAGING_KERNEL_DIR} --without-x > ac_cv_pr

[OE-core] oprofile rebuilds for different MACHINES (sstate)

2015-08-11 Thread Denys Dmytriyenko
So, I've been debugging the issue of oprofile rebuilding from one MACHINE to another (causing PR issues, etc). I was able to trace it down to this line: EXTRA_OECONF = "--with-kernel=${STAGING_KERNEL_DIR} --without-x ac_cv_prog_XSLTPROC=" And STAGING_KERNEL_DIR resolves to this: STAGING_KERNE