From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] trace-cmd: add missing host-swig dependency
Date: Mon, 27 Apr 2015 11:54:35 +0200 [thread overview]
Message-ID: <20150427095435.GH28533@pengutronix.de> (raw)
In-Reply-To: <20150427092316.GC27628@omega>
On Mon, Apr 27, 2015 at 11:23:17AM +0200, Alexander Aring wrote:
> 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.
Well, things are not quite that simple. It depends on the use-case. Using
'select' only works correctly, when the selected option does not depend on
anything with 'depends on'. I the kernel that is usually a problem, so
'select' is avoided. In ptxdist, the toplevel options usually don't have
any 'depends on' so we can use 'select' here.
There are some exceptions and they cause problems occasionally :-)
> 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'.
We organize the options in PTXdist in a way, so that a simple select is
(usually) enough.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-04-27 9:54 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
2015-04-27 9:54 ` Michael Olbrich [this message]
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=20150427095435.GH28533@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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