[Buildroot] Buildroot now requires IPv6?

[Buildroot] Buildroot now requires IPv6?

[Grant Edwards]

The products for which I use buildroot do not have IPv6 support
(that's in the product requirements).  However, it appears that more
recent versions of Buildroot now force you to use a toolchain with
IPv6 support in the C library even if no applications uses IPv6 and
the kernel doesn't support IPV6.

Do I understand this correctly?

-- 
Grant Edwards               grant.b.edwards        Yow! Let's send the
                                  at               Russians defective
                              gmail.com            lifestyle accessories!

[Buildroot] Buildroot now requires IPv6?

[Baruch Siach]

Hi Grant,

On Mon, Jul 11, 2016 at 04:33:22PM +0000, Grant Edwards wrote:
> The products for which I use buildroot do not have IPv6 support
> (that's in the product requirements).  However, it appears that more
> recent versions of Buildroot now force you to use a toolchain with
> IPv6 support in the C library even if no applications uses IPv6 and
> the kernel doesn't support IPV6.
> 
> Do I understand this correctly?

That's correct. The CHANGES entry for 2015.05-rc1 reads:

  Toolchains: IPv6 and Largefile support now enforced for
  uClibc. Corresponding Kconfig symbols removed.

Only uClibc is mentioned here because other C libraries already enable IPv6 
unconditionally.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

[Buildroot] Buildroot now requires IPv6?

[Yann E. MORIN]

Grant, Baruch,

On 2016-07-11 19:43 +0300, Baruch Siach spake thusly:
> On Mon, Jul 11, 2016 at 04:33:22PM +0000, Grant Edwards wrote:
> > The products for which I use buildroot do not have IPv6 support
> > (that's in the product requirements).  However, it appears that more
> > recent versions of Buildroot now force you to use a toolchain with
> > IPv6 support in the C library even if no applications uses IPv6 and
> > the kernel doesn't support IPV6.
> > 
> > Do I understand this correctly?
> 
> That's correct. The CHANGES entry for 2015.05-rc1 reads:
> 
>   Toolchains: IPv6 and Largefile support now enforced for
>   uClibc. Corresponding Kconfig symbols removed.
> 
> 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. 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.

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

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Buildroot now requires IPv6?

[Grant Edwards]

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!!