From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libwebsockets: add option to enable/disable ipv6 support
Date: Wed, 23 Sep 2015 23:02:36 +0200 [thread overview]
Message-ID: <20150923230236.5b5c5302@free-electrons.com> (raw)
In-Reply-To: <1443014194-24211-1-git-send-email-andreas.wetzel@nanotronic.ch>
Dear Andreas Wetzel,
On Wed, 23 Sep 2015 15:16:34 +0200, Andreas Wetzel wrote:
> Added configuration option BR2_PACKAGE_LIBWEBSOCKETS_IPV6 that
> adds -DLWS_IPV6=ON/OFF to LIBWEBSOCKETS_CONF_OPTS.
>
> Signed-off-by: Andreas Wetzel <andreas.wetzel@nanotronic.ch>
We stopped supporting IPv6 as an optional feature in the toolchain, and
made it mandatory. So, to go in the same direction, I would suggest to
simply always enable IPv6 in libwebsockets.
What is the size overhead of enabling IPv6 ? If it's reasonable, then
we want IPv6 to be unconditionally enabled.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-23 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 13:16 [Buildroot] [PATCH 1/1] libwebsockets: add option to enable/disable ipv6 support Andreas Wetzel
2015-09-23 14:08 ` Vicente Olivert Riera
2015-09-23 14:43 ` Wetzel Andreas
2015-09-23 14:51 ` Vicente Olivert Riera
2015-09-23 15:12 ` Wetzel Andreas
2015-09-23 15:42 ` Vicente Olivert Riera
2015-09-23 21:02 ` Thomas Petazzoni [this message]
2015-09-25 11:12 ` Wetzel Andreas
2015-09-25 12:06 ` Thomas Petazzoni
2015-09-25 12:27 ` Gustavo Zacarias
2015-09-25 12:33 ` Thomas Petazzoni
2015-10-03 18:57 ` Peter Korsgaard
2015-10-05 8:18 ` Wetzel Andreas
2015-10-10 17:24 ` Thomas Petazzoni
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=20150923230236.5b5c5302@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox