On Tue, Aug 14, 2012 at 11:29 PM, McClintock Matthew-B29882 <[email protected]> wrote: > > On Aug 14, 2012 10:11 PM, "Bruce Ashfield" <[email protected]> wrote: >> >> On Tue, Aug 14, 2012 at 6:39 PM, McClintock Matthew-B29882 >> <[email protected]> wrote: >> > I've had to fix / hack the perf_3.4.bb recipe to get it building on my >> > older kernel. Should we add perf_3.0.bb recipes in oe-core or my own >> > layer? Or try to keep one recipe working for all versions? I have no >> > strong opinions. >> >> I'd prefer one recipe. Liang sent another proposal earlier for a fix >> that should make >> it work on all kernels. Just waiting to hear on that at the moment. > > I've actually got other issues...
Did you post the error and I missed it .. I block marked quite a few email read earlier :) In that case, we can factor out common code to a .inc and keep the changes between versions as small as possible. Cheers, Bruce > > -M > >> >> Cheers, >> >> Bruce >> >> > >> > -M >> > >> > _______________________________________________ >> > Openembedded-core mailing list >> > [email protected] >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> >> >> >> -- >> "Thou shalt not follow the NULL pointer, for chaos and madness await >> thee at its end" >> >> _______________________________________________ >> Openembedded-core mailing list >> [email protected] >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > > > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
