mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Cc: Alexander Aring <alex.aring@gmail.com>
Subject: [ptxdist] [PATCH] trace-cmd: add missing host-swig dependency
Date: Mon, 20 Apr 2015 09:48:45 +0200	[thread overview]
Message-ID: <1429516125-20448-1-git-send-email-alex.aring@gmail.com> (raw)

This patch adds a missing host-swig dependency which is needed by
trace-cmd to generate some python bindings. Without host-swig I get the
following compile error:

LD PLUGIN           plugin_sched_switch.so
  BUILD PLUGIN           plugin_mac80211.so
  BUILD PLUGIN           plugin_function.so
swig -Wall -python -noproxy ctracecmd.i
  BUILD PLUGIN           plugin_jbd2.so
make[1]: swig: Command not found
Makefile:581: recipe for target 'ctracecmd.so' failed
make[1]: *** [ctracecmd.so] Error 127
make[1]: *** Waiting for unfinished jobs....

Signed-off-by: Alexander Aring <alex.aring@gmail.com>
---
 rules/trace-cmd.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/rules/trace-cmd.in b/rules/trace-cmd.in
index 5c1d37a..d06fe25 100644
--- a/rules/trace-cmd.in
+++ b/rules/trace-cmd.in
@@ -5,6 +5,10 @@ config TRACE_CMD
 	prompt "trace-cmd"
 	select LIBC_DL
 	select GCCLIBS_GCC_S
+	select HOST_SWIG
+	select HOST_ZLIB
+	select HOST_LIBPCRE
+	select HOST_PYTHON
 	help
 	  The trace-cmd command interacts with the Ftrace tracer that
 	  is built inside the Linux kernel. It interfaces with the
-- 
2.3.5


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2015-04-20  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  7:48 Alexander Aring [this message]
2015-04-27  8:56 ` Michael Olbrich
2015-04-27  9:23   ` Alexander Aring
2015-04-27  9:54     ` Michael Olbrich

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=1429516125-20448-1-git-send-email-alex.aring@gmail.com \
    --to=alex.aring@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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