Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] add libaudit and enable 'perf trace'
Date: Wed, 27 Feb 2013 13:53:36 -0600	[thread overview]
Message-ID: <1361994816.2588.0.camel@empanada> (raw)
In-Reply-To: <CAHUNapSHx-HAK86oQQWG9hYwa_zV11ccqs-i5GxUA+ztjvBNAA@mail.gmail.com>

On Wed, 2013-02-27 at 13:00 -0500, Trevor Woerner wrote:
> On Wed, Feb 27, 2013 at 10:00 AM,  <tom.zanussi@linux.intel.com> wrote:
> > From: Tom Zanussi <tom.zanussi@linux.intel.com>
> >
> > 'perf-trace' is a new perf subcommand available in the 3.8 kernel -
> > this patchset enables it.  'perf trace' requires libaudit, which
> > is added as a new recipe.
> 
> (I'm just getting used to this workflow, so sorry if I've messed
> something up on my end)
> 
> When I try to build with just the following added to my conf/local.conf
> 
>     IMAGE_INSTALL_append = " perf"
> 
> I get the following error:
> 
> Build Configuration:
> BB_VERSION        = "1.17.1"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "SUSE-LINUX-12.2"
> TARGET_SYS        = "i586-poky-linux"
> MACHINE           = "qemux86"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.3+snapshot-20130227"
> TUNE_FEATURES     = "m32 i586"
> TARGET_FPU        = ""
> meta
> meta-yocto
> meta-yocto-bsp    =
> "tzanussi/perf-trace-v1:9f91a3a29701218dd756380ebcd2a1a32ad40615"
> 
> Computing transaction...error: Can't install perf-3.4-r9@qemux86: no
> package provides /bin/bash
> ERROR: Function failed: do_rootfs
> 

Hmm, I didn't realize perf required 'bash' to build.  I always build
core-image-sato with tools-profile or the sdk image, and haven't seen
this.

Which image are you building?  I'm guessing core-image-minimal?

I think if perf doesn't build without bash, it should be considered a
bug - core-image-minimal should be able to use perf.

Tom 


> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





  parent reply	other threads:[~2013-02-27 20:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 15:00 [PATCH 0/3] add libaudit and enable 'perf trace' tom.zanussi
2013-02-27 15:00 ` [PATCH 1/3] libaudit: new package tom.zanussi
2013-02-28  4:32   ` Saul Wold
2013-02-28  4:45     ` Tom Zanussi
2013-02-28 18:57       ` Saul Wold
2013-02-28 19:44         ` Tom Zanussi
2013-02-28 21:01           ` Richard Purdie
2013-02-28 21:14             ` Tom Zanussi
2013-03-01 23:00               ` Burton, Ross
2013-03-01 22:45             ` Colin Walters
2013-02-27 15:00 ` [PATCH 2/3] perf: add perf-trace feature tom.zanussi
2013-02-27 15:00 ` [PATCH 3/3] perf: enable " tom.zanussi
2013-02-27 18:00 ` [PATCH 0/3] add libaudit and enable 'perf trace' Trevor Woerner
     [not found]   ` <1361988753.1704.4.camel@empanada>
2013-02-27 18:22     ` Trevor Woerner
2013-02-27 19:53   ` Tom Zanussi [this message]
2013-02-27 18:10 ` Trevor Woerner
2013-02-27 19:54   ` Tom Zanussi
2015-08-15 23:33 ` Christian Ascheberg

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=1361994816.2588.0.camel@empanada \
    --to=tom.zanussi@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox