mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] trace-cmd: add missing host-swig dependency
Date: Mon, 27 Apr 2015 11:23:17 +0200	[thread overview]
Message-ID: <20150427092316.GC27628@omega> (raw)
In-Reply-To: <20150427085628.GE28533@pengutronix.de>

Hi Michael,

On Mon, Apr 27, 2015 at 10:56:28AM +0200, Michael Olbrich wrote:
> On Mon, Apr 20, 2015 at 09:48:45AM +0200, Alexander Aring wrote:
> > 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:
> 
> I've changed this to just select HOST_SWIG. The others should not be
> necessary. Can you confirm that it still works? Maybe you didn't run
> 'oldconfig'?
> 

I need to admit, I was not sure about to handle this. I learned that
"select" is in Kconfig an evil statement for doing selection on config
entries which has also others "select/depends on" statements. Maybe this
is only if the selected statement has a "depends on" only or ptxdist can
handle this.

A "depends on" doesn't work here because it's noprompt. Now I realized
that when I try to add all HOST_SWIG dependencies then this doesn't work
because select doesn't give any information about the order on which
dependency should be compiled at first.

Anyway these thinking about that confused me and I would say that a
simple "select HOST_SWIG" is enough than I will trust you. I tested it
and after running 'oldconfig' it works, also fine with the dependencies
like 'host-libpcre'.

Thanks.

- Alex

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-04-27  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  7:48 Alexander Aring
2015-04-27  8:56 ` Michael Olbrich
2015-04-27  9:23   ` Alexander Aring [this message]
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=20150427092316.GC27628@omega \
    --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