From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 toolchain build failure
Date: Wed, 13 Nov 2013 22:36:46 +0100 [thread overview]
Message-ID: <20131113223646.66a7a61b@skate> (raw)
Hello Simon,
I've tried to build an AVR32 toolchain with 2013.11-rc1, with the
following defconfig:
BR2_avr32=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_TOOLCHAIN_BUILDROOT_INET_IPV6=y
BR2_TOOLCHAIN_BUILDROOT_INET_RPC=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_INIT_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
# BR2_TARGET_ROOTFS_TAR is not set
and the build failed with:
In file included from /opt/br-avr32-full-2013.11-rc1/usr/avr32-buildroot-linux-uclibc/sysroot/usr/include/linux/kernel.h:4,
from /opt/br-avr32-full-2013.11-rc1/usr/avr32-buildroot-linux-uclibc/sysroot/usr/include/linux/netlink.h:4,
from /opt/br-avr32-full-2013.11-rc1/usr/avr32-buildroot-linux-uclibc/sysroot/usr/include/linux/rtnetlink.h:5,
from libc/inet/netlinkaccess.h:27,
from libc/inet/if_index.c:36:
/opt/br-avr32-full-2013.11-rc1/usr/avr32-buildroot-linux-uclibc/sysroot/usr/include/linux/sysinfo.h:8: error: expected specifier-qualifier-list before '__kernel_long_t'
make[1]: *** [libc/inet/if_index.os] Error 1
make[1]: Leaving directory `/opt/toolchain-build/build/uclibc-0.9.31.1'
It is apparently reported at:
https://lkml.org/lkml/2013/5/18/1
However, I've also built several other toolchains with the same
Buildroot version and haven't had any problem.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2013-11-13 21:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 21:36 Thomas Petazzoni [this message]
2013-11-14 8:53 ` [Buildroot] AVR32 toolchain build failure Simon Dawson
2013-11-14 9:10 ` Thomas Petazzoni
2013-11-15 8:58 ` Simon Dawson
-- strict thread matches above, loose matches on Subject: below --
2013-08-05 12:01 Thomas De Schampheleire
2013-08-05 12:29 ` Thomas De Schampheleire
2013-08-06 9:27 ` Alexander Lukichev
2013-08-06 9:39 ` Alexander Lukichev
2013-08-06 14:40 ` Thomas De Schampheleire
2013-08-06 15:03 ` Thomas De Schampheleire
2013-08-08 15:35 ` Alexander Lukichev
2013-08-06 17:54 ` Thomas Petazzoni
2013-08-06 19:33 ` Thomas De Schampheleire
2013-08-07 7:05 ` Thomas De Schampheleire
2013-08-07 15:20 ` Thomas Petazzoni
2013-08-07 16:01 ` Thomas De Schampheleire
2013-08-07 18:20 ` Thomas De Schampheleire
2013-08-07 22:07 ` Thomas Petazzoni
2013-08-08 5:55 ` Thomas De Schampheleire
2013-08-08 7:21 ` Simon Dawson
2013-08-08 8:03 ` Thomas Petazzoni
2013-08-08 10:56 ` Gustavo Zacarias
2013-08-08 16:18 ` Simon Dawson
2013-08-08 17:57 ` Gustavo Zacarias
2013-08-08 17:59 ` Thomas Petazzoni
2013-08-13 6:15 ` Arnout Vandecappelle
2013-08-08 8:12 ` Thomas De Schampheleire
2013-08-08 16:09 ` Simon Dawson
2013-08-08 17:34 ` Thomas De Schampheleire
2013-08-08 17:57 ` Thomas Petazzoni
2013-08-08 18:05 ` Thomas De Schampheleire
2013-08-08 19:42 ` Simon Dawson
2013-08-08 20:09 ` Thomas De Schampheleire
2013-08-08 20:24 ` Thomas De Schampheleire
2013-08-08 22:22 ` Thiago A. Corrêa
2013-08-09 4:51 ` Alexander Lukichev
2013-08-09 7:16 ` Simon Dawson
2013-08-09 11:12 ` Thomas De Schampheleire
2013-08-09 20:29 ` Thomas Petazzoni
2013-08-09 22:34 ` Gustavo Zacarias
2013-08-08 7:29 ` Alexander Lukichev
2013-08-08 8:13 ` Thomas De Schampheleire
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=20131113223646.66a7a61b@skate \
--to=thomas.petazzoni@free-electrons.com \
--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