From: Tom Zanussi <tom.zanussi@intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/1] linux-yocto: temporary NO_LIBPERL fix for perf
Date: Fri, 14 Jan 2011 16:49:48 -0600 [thread overview]
Message-ID: <cover.1295044979.git.tom.zanussi@intel.com> (raw)
I'm not familiar enough with the perf recipe to come up with a proper
fix for the problem yet, but this patch at least removes the build
error that recently started happening with the linux-yocto perf
compile.
I'll send a patch re-instating the code it removes once I've
understood the perf recipe and root-caused the problem. In any case,
it doesn't remove any functionality that was there before - NO_LIBPERL
was always the case, but the code that made that happen just started
blowing up for some reason.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: tzanussi/perf-no-libperl-fix
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tzanussi/perf-no-libperl-fix
Thanks,
Tom Zanussi <tom.zanussi@intel.com>
---
Tom Zanussi (1):
linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON
.../linux-yocto/tools-perf-no-scripting.patch | 49 ++++++++++++++++++++
meta/recipes-kernel/linux/linux-yocto_git.bb | 5 +-
2 files changed, 52 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-kernel/linux/linux-yocto/tools-perf-no-scripting.patch
next reply other threads:[~2011-01-14 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 22:49 Tom Zanussi [this message]
2011-01-14 22:49 ` [PATCH 1/1] linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON Tom Zanussi
2011-01-15 2:46 ` [PATCH 0/1] linux-yocto: temporary NO_LIBPERL fix for perf Bruce Ashfield
2011-01-15 3:43 ` Tom Zanussi
2011-01-15 3:56 ` Bruce Ashfield
2011-01-15 4:14 ` 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=cover.1295044979.git.tom.zanussi@intel.com \
--to=tom.zanussi@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.