Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8736] IPV6 forced on in busybox
Date: Fri, 04 Mar 2016 16:10:53 +0000	[thread overview]
Message-ID: <bug-8736-163-AEGNMiPg3n@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8736-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=8736

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #10 from Peter Korsgaard <jacmet@uclibc.org> ---
Fixed in git by:

commit 7a5be2a042f3c1d55c5599ad819333a2150955ff
Author: Peter Korsgaard <peter@korsgaard.com>
Date:   Fri Mar 4 16:47:38 2016 +0100

    busybox: tweak IPv6/largefile handling

    Fixes #8736

    When IPv6 and largefile options were removed from Buildroot, the code to
    force these options in busybox were still left in.

    There's no strong reason to forcefully enable these options (only to
disable
    options if the system cannot support it like we do for nommu), so instead
    enable the options in our default defconfig, allowing people to override
    this if they use a custom config.

    While we're at it, enable the prefer-ipv4 option so network applets like
    ntpd doesn't fail when dual stacked hosts are resolved from a system
without
    IPv6 support enabled in the kernel.

    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2016-03-04 16:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 17:07 [Buildroot] [Bug 8736] New: IPV6 forced on in busybox bugzilla at busybox.net
2016-03-03 20:59 ` [Buildroot] [Bug 8736] " bugzilla at busybox.net
2016-03-03 21:08   ` Grant Edwards
2016-03-03 21:12     ` Peter Korsgaard
2016-03-03 21:15     ` Peter Korsgaard
2016-03-03 21:35       ` Grant Edwards
2016-03-03 21:05 ` bugzilla at busybox.net
2016-03-03 21:09 ` bugzilla at busybox.net
2016-03-03 21:13 ` bugzilla at busybox.net
2016-03-03 21:17 ` bugzilla at busybox.net
2016-03-03 21:43 ` bugzilla at busybox.net
2016-03-03 21:47 ` bugzilla at busybox.net
2016-03-03 22:33 ` bugzilla at busybox.net
2016-03-03 22:40 ` bugzilla at busybox.net
2016-03-04 16:10 ` bugzilla at busybox.net [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=bug-8736-163-AEGNMiPg3n@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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