From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8736] IPV6 forced on in busybox
Date: Thu, 03 Mar 2016 21:05:45 +0000 [thread overview]
Message-ID: <bug-8736-163-Yw8am9oihc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8736-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8736
--- Comment #2 from Kenric Smith <ksmith@aesaustin.com> ---
Sorry for the confusion. Busybox is acting as it should, the issue is that
Buildroot is telling Busybox to enable IPV6 no matter what. For Buildroot
systems where IPV6 is not enabled (in the kernel), Buildroot shouldn't enable
IPV6 in Busybox.
Previously it appears that IPV6 was a Buildroot configuration option and that
option was properly being passed into Busybox. When that option was removed,
IPV6 was forced on in Busybox by the Buildroot configuration.
The patch attached just allows Busybox to be configured or not for IPV6, in the
menuconfig option of Busybox, instead of forcing it to be enabled in Busybox.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-03-03 21:05 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 [this message]
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
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-Yw8am9oihc@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