From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: How to deal with ERROR: Nothing RPROVIDES 'perf'
Date: Wed, 20 Apr 2011 16:17:13 -0700 [thread overview]
Message-ID: <1303341434.2893.23.camel@scimitar> (raw)
In-Reply-To: <BANLkTinU+JDgmJkcNp60aR5LEwX2uCCbvA@mail.gmail.com>
On Wed, 2011-04-20 at 20:55 +0200, Francis Meyvis wrote:
> Hello,
>
> I'm using yocto's bernard and trying to build for an arm board (igep0020).
> For this I created meta/conf/machines/igep0020.conf.
> And my build/conf/local.conf's MACHINE is set as ipep0020
> As a start I used the content of the existing beagleboard.conf for igep0020.conf
> I have also this line in my local.conf:
> EXTRA_IMAGE_FEATURES = "dbg-pkgs dev-pkgs tools-sdk tools-debug
> tools-profile tools-testapps debug-tweaks"
>
> A bitbake seems to fail each time with these messages below.
> If I limit the EXTRA_IMAGE_FEATURES as follows "dbg-pkgs dev-pkgs
> tools-sdk debug-tweaks" building starts
> But I'm keen on also having debugging tools available (like strace) on
> the target ...
>
> What am I missing? Thanks
I'm not too familiar with the igep layer, I assume it's not using the
one of the yocto-linux kernel recipes?
perf must be enabled in individual kernel recipes, the yocto kernels do
this through the inherited linux-tools.inc
> Should I also post my problem on the yocto mailing list?
This list is the right one for build system issues :-)
Regards,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-04-20 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 18:55 How to deal with ERROR: Nothing RPROVIDES 'perf' Francis Meyvis
2011-04-20 23:17 ` Joshua Lock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1303341434.2893.23.camel@scimitar \
--to=josh@linux.intel.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.