From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using linux-zigbee ?
Date: Fri, 21 Jul 2017 08:48:23 +0200 [thread overview]
Message-ID: <20170721084823.0fca155c@windsurf> (raw)
In-Reply-To: <20170721035311.lj4g7b4fugewmr55@tarshish>
Hello,
On Fri, 21 Jul 2017 06:53:11 +0300, Baruch Siach wrote:
> > In addition, linux-zigbee now fails to build with gcc 7.x:
> > http://autobuild.buildroot.net/results/29c/29c72bc38042305310576be945c721b2fad95894/build-end.log.
>
> The fix[1] for that (remove -Werror) is quite easy, you don't even need to
> patch the code.
Ah, yes, I missed the fact that it was a warning-turned-into-an-error
class of problem. Thanks for spotting this!
> > Do you still use linux-zigbee ? Or could we remove it from Buildroot in
> > favor of wpan-tools ?
>
> Buildroot carries packages that are deprecated/abandoned for much longer than
> that (e.g. wireless_tools). The command line interface difference between
> linux-zigbee and wpan-tools is a good enough reason to keep linux-zigbee, IMO.
True, but at some point, we'll have to get rid of some old unmaintained
packages.
Perhaps we should at least update the help text of linux-zigbee to make
it clear it shouldn't be used for new projects ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-21 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 20:57 [Buildroot] Using linux-zigbee ? Thomas Petazzoni
2017-07-21 3:53 ` Baruch Siach
2017-07-21 6:48 ` Thomas Petazzoni [this message]
2017-07-21 6:50 ` Maxime Hadjinlian
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=20170721084823.0fca155c@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.