Since the introduction of 4.11 kernel headers in Buildroot, radvd has failed to build with all toolchains using this kernel header version. The issue comes from the fact that radvd includes both <net/if_arp.h> and <linux/if_arp.h> if they are available. Until 4.11, <linux/if_arp.h> was in fact not included, because the AC_CHECK_HEADERS() test concluded this header was unsuitable. This has been fixed in the upstream kernel by commit 2618be7dccf8739b89e1906b64bd8d551af351e6 ("uapi: fix linux/if.h userspace compilation errors"). So now, the radvd configure script considers both <net/if_arp.h> and <linux/if_arp.h> as suitable headers, and includes both of them, leading to the duplicate definition of various types. Since it's redundant to include both <net/if_arp.h> and <linux/if_arp.h>, we simply force radvd to believe that <linux/if_arp.h> is not available by passing the appropriate autoconf cache variable. This gets us back to the previous situation, where <linux/if_arp.h> was never used. This has been tested with a uClibc toolchain using 4.11 kernel headers, and verified to work on glibc and musl with older kernel headers as well. Fixes: http://autobuild.buildroot.net/results/949a75d96299394e4ac957746fa23a4b52f31b43/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
---|---|---|
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
.defconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitlab-ci.yml.in | ||
CHANGES | ||
Config.in | ||
Config.in.legacy | ||
COPYING | ||
DEVELOPERS | ||
Makefile | ||
Makefile.legacy | ||
README |
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on Freenode IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches