From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8736] New: IPV6 forced on in busybox
Date: Thu, 03 Mar 2016 17:07:18 +0000 [thread overview]
Message-ID: <bug-8736-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8736
Bug ID: 8736
Summary: IPV6 forced on in busybox
Product: buildroot
Version: 2015.11
Hardware: Other
OS: Linux
Status: NEW
Severity: trivial
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ksmith at aesaustin.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 6371
--> https://bugs.busybox.net/attachment.cgi?id=6371&action=edit
Patch to package makefile to remove forcing IPV6
It appears from the commit logs that the IPV6 config option was removed for
buildroot, but the remnants of the removal are forcing FEATURE_IPV6 in busybox.
The attached patch would remove setting that feature in busybox.
Without this patch, the ntpd applet in busybox doesn't function properly,
attempting to contact IPV6 hosts.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-03-03 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 17:07 bugzilla at busybox.net [this message]
2016-03-03 20:59 ` [Buildroot] [Bug 8736] IPV6 forced on in busybox 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
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@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