From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8016] New: collectd fails to build, network.c:171:19: error: 'IPV6_MULTICAST_HOPS' undeclared
Date: Wed, 15 Apr 2015 18:15:20 +0000 (UTC) [thread overview]
Message-ID: <bug-8016-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8016
Summary: collectd fails to build, network.c:171:19: error:
'IPV6_MULTICAST_HOPS' undeclared
Product: buildroot
Version: 2015.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: kdankwardt at xpliant.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5996
--> https://bugs.busybox.net/attachment.cgi?id=5996
The buildroot .config file
Trying to build an x86_64 toolchain on x86_64.
make[5]: Entering directory
'/home/kevin/x86_64-toolchain/buildroot/output/build/collectd-5.4.2/src/libcollectdclient'
CC libcollectdclient_la-client.lo
CC libcollectdclient_la-network.lo
CC libcollectdclient_la-network_buffer.lo
network.c: In function 'server_open_socket':
network.c:171:19: error: 'IPV6_MULTICAST_HOPS' undeclared (first use in this
function)
optname = IPV6_MULTICAST_HOPS;
^
network.c:171:19: note: each undeclared identifier is reported only once for
each function it appears in
network.c:173:19: error: 'IPV6_UNICAST_HOPS' undeclared (first use in this
function)
optname = IPV6_UNICAST_HOPS;
^
Makefile:570: recipe for target 'libcollectdclient_la-network.lo' failed
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-04-15 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 18:15 bugzilla at busybox.net [this message]
2015-04-16 12:15 ` [Buildroot] [Bug 8016] collectd fails to build, network.c:171:19: error: 'IPV6_MULTICAST_HOPS' undeclared 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-8016-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.