From: Alexander Aring <alex.aring@gmail.com>
To: "Jürgen Beisert" <jbe@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] lowpan-tools: update lowpan-patches
Date: Mon, 6 Jan 2014 09:25:08 +0100 [thread overview]
Message-ID: <20140106082507.GA12646@omega> (raw)
In-Reply-To: <201401060840.24805.jbe@pengutronix.de>
Hi Jürgen,
On Mon, Jan 06, 2014 at 08:40:24AM +0100, Jürgen Beisert wrote:
> Hi Alexander,
>
> On Monday 13 May 2013 17:00:36 Michael Olbrich wrote:
> > On Mon, May 13, 2013 at 02:38:10PM +0200, Alexander Aring wrote:
> > > Currently there is no way to make a new lowpan-tools release.
> > > This patch synchronize the patches from version 0.3 with current
> > > git master.
> > >
> > > Delete Patch 0001-Avoid-crashing-in-izcoordinator.patch. Which is
> > > replaced by upstream 0001-izoordinator-Fixes-to-error-handling.patch
> > > patch.
> >
> > Thanks, applied.
>
> This package fails in the prepare stage when the LOWPAN_TOOLS_TESTS is not set.
> The 'configure' script always checks for python.
>
> I do not know yet how this package depends on python: Should we always build
> python in order to make this package build again or should we add a new
> parameter to its configure.ac to switch off this test, when the test tools are
> disabled?
>
indeed. The 'configure' script always checks for python and generate a
python 'site-package module'.
The LOWPAN_TOOLS_TESTS needs this 'module' only. But at the moment there
is no 'enable/disable' switch in the 'configure' script.
We shall change:
"select PYTHON if LOWPAN_TOOLS_TESTS" to "select PYTHON"
Thanks for the hint!
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-06 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 12:38 Alexander Aring
2013-05-13 15:00 ` Michael Olbrich
2014-01-06 7:40 ` Jürgen Beisert
2014-01-06 8:25 ` Alexander Aring [this message]
2014-01-06 10:50 ` Michael Olbrich
2014-01-06 11:20 ` Jürgen Beisert
2014-01-06 11:51 ` 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=20140106082507.GA12646@omega \
--to=alex.aring@gmail.com \
--cc=jbe@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