From: Marty <marty@heavyreckoning.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] Forum for LEDE build env questions?
Date: Tue, 21 Feb 2017 11:23:41 -0500 [thread overview]
Message-ID: <105da92d-3a20-b67e-1e7e-71d1df85fe28@heavyreckoning.com> (raw)
I'm snagging on the MUSL redefinition errors when building LEDE image
and build tools.
/home/marty/lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl_eabi/include/linux/in6.h:32:8:
error: redefinition of 'struct in6_addr'
/home/marty/lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl_eabi/include/linux/in6.h:49:8:
error: redefinition of 'struct sockaddr_in6'
/home/marty/lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl_eabi/include/linux/in6.h:59:8:
error: redefinition of 'struct ipv6_mreq'
I want to ask if it is a simple .config issue via make menuconfig, an
include path issue during compile, a linux header issue, etc. But I want
to ask in the right place.
TIA,
Marty
next reply other threads:[~2017-02-21 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 16:23 Marty [this message]
2017-02-21 16:50 ` David Lang
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=105da92d-3a20-b67e-1e7e-71d1df85fe28@heavyreckoning.com \
--to=marty@heavyreckoning.com \
--cc=make-wifi-fast@lists.bufferbloat.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