From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] systemtap: fix docproc build error
Date: Sat, 14 Apr 2012 14:39:52 +0100 [thread overview]
Message-ID: <1334410792.7309.104.camel@ted> (raw)
In-Reply-To: <e1cc1d55074d9755f1e7e20a3b07718b40cb9515.1334346682.git.tom.zanussi@intel.com>
On Fri, 2012-04-13 at 14:56 -0500, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> When building docs in systemtap, docproc is used to generate the
> tapset documentation, but it gets built for the target, while it needs
> to be build for the host instead. This change causes that to happen.
>
> Fixes [YOCTO #2193].
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> .../systemtap/systemtap/docproc-build-fix.patch | 19 +++++++++++++++++++
> meta/recipes-kernel/systemtap/systemtap_git.bb | 6 +++++-
> meta/recipes-kernel/systemtap/systemtap_git.inc | 4 +++-
> 3 files changed, 27 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-kernel/systemtap/systemtap/docproc-build-fix.patch
This broke systemtap-uprobes. I've pushed a fix:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=45da10943965193fd2d14b756b95e6f0f4ae9029
Cheers,
Richard
next prev parent reply other threads:[~2012-04-14 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 19:55 [PATCH 0/2] systemtap doc build fix tom.zanussi
2012-04-13 19:56 ` [PATCH 1/2] systemtap: fix docproc build error tom.zanussi
2012-04-14 13:39 ` Richard Purdie [this message]
2012-04-13 19:56 ` [PATCH 2/2] systemtap: disable document generation by default tom.zanussi
2012-04-16 15:40 ` [PATCH 0/2] systemtap doc build fix 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=1334410792.7309.104.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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.