Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot now requires IPv6?
Date: Tue, 12 Jul 2016 17:05:17 +0000 (UTC)	[thread overview]
Message-ID: <nm380d$ipv$1@ger.gmane.org> (raw)
In-Reply-To: 20160712164820.GC3680@free.fr

On 2016-07-12, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
>> Only uClibc is mentioned here because other C libraries already enable IPv6 
>> unconditionally.
>
> But nothing prevents you from running on a kernel that does not have
> IPv6.

Cool. That's what I was planning on doing, but I hadn't tried it yet.

> The requirements are only about IPv6 support in the toolchain.

> Maintaining support for non-IPv6 toolchains was becoming quite a
> problem, as more and more packages were breaking with such toolchains.

That's understandable.

> And come on, we're in 2016, there is no more IPv4 available, it's time
> to switch over to IPV6! ;-]

The devices I use buildroot for are never connected to the Internet.
Most of the time they're on an air-gapped network with at most a dozen
or two nodes -- so IPv4 works fine.

Although using IPv6 with link-local addresses and auto-discovery would
be even better, these customer are just barely getting the hang of
Ethernet and IPv4...

-- 
Grant Edwards               grant.b.edwards        Yow! My CODE of ETHICS
                                  at               is vacationing at famed
                              gmail.com            SCHROON LAKE in upstate
                                                   New York!!

      reply	other threads:[~2016-07-12 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 16:33 [Buildroot] Buildroot now requires IPv6? Grant Edwards
2016-07-11 16:43 ` Baruch Siach
2016-07-12 16:48   ` Yann E. MORIN
2016-07-12 17:05     ` Grant Edwards [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='nm380d$ipv$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.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