From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org, liang.li@windriver.com
Cc: saul.wold@intel.com
Subject: Re: [PATCH 2/3] recipes-kernel: make perf a standalone package
Date: Wed, 20 Jun 2012 16:25:45 +0100 [thread overview]
Message-ID: <1472036.VpViiY8Ijl@helios> (raw)
In-Reply-To: <6e8878c5f3598b60d364e2656af74e9f712770ca.1340201997.git.bruce.ashfield@windriver.com>
On Wednesday 20 June 2012 10:31:40 Bruce Ashfield wrote:
> From: Liang Li <liang.li@windriver.com>
>...
> +EXTRA_OEMAKE = \
> + '-C ${S}/tools/perf \
> + O=${B} \
> + CROSS_COMPILE=${TARGET_PREFIX} \
> + ARCH=${ARCH} \
> + CC="${CC}" \
> + AR="${AR}" \
> + prefix=/usr \
> + NO_GTK2=1 NO_NEWT=1 NO_DWARF=1 \
Coincidentally, I've just noticed that the current (kernel integrated) perf
package can sometimes depend on gtk+/glib-2.0 or not depending on whether
these are available when the kernel is built. Presumably NO_GTK2=1 above
disables gtk+ support and thus would prevent this?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-20 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:31 [v2 PATCH 0/3] perf: make perf a standlone recipe Bruce Ashfield
2012-06-20 14:31 ` [PATCH 1/3] kernel: save $kerndir/tools and $kerndir/lib from pruning Bruce Ashfield
2012-06-20 14:31 ` [PATCH 2/3] recipes-kernel: make perf a standalone package Bruce Ashfield
2012-06-20 15:00 ` Saul Wold
2012-06-20 15:02 ` Bruce Ashfield
2012-06-20 15:25 ` Paul Eggleton [this message]
2012-06-20 15:27 ` Bruce Ashfield
2012-06-20 14:31 ` [PATCH 3/3] recipes-kernel: remove linux-tools.inc Bruce Ashfield
2012-06-22 18:00 ` [v2 PATCH 0/3] perf: make perf a standlone recipe Saul Wold
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=1472036.VpViiY8Ijl@helios \
--to=paul.eggleton@linux.intel.com \
--cc=liang.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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