From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] avr32: disable kernel headers
Date: Fri, 8 Nov 2013 08:22:43 +0100 [thread overview]
Message-ID: <20131108082243.1a889fee@skate> (raw)
In-Reply-To: <1383859843-3549-1-git-send-email-spdawson@gmail.com>
Simon,
On Thu, 7 Nov 2013 21:30:43 +0000, spdawson at gmail.com wrote:
> From: Simon Dawson <spdawson@gmail.com>
>
> Using kernel headers newer than 3.6.x, uclibc fails to build:
>
> In file included from output/host/usr/avr32-buildroot-linux-uclibc/sysroot/usr/include/linux/rtnetlink.h:6,
> from libc/inet/netlinkaccess.h:34,
> from libc/inet/if_index.c:36:
> output/host/usr/avr32-buildroot-linux-uclibc/sysroot/usr/include/linux/if_link.h:314: error: expected specifier-qualifier-list before '__be16'
> make[1]: *** [libc/inet/if_index.os] Error 1
> make[1]: Leaving directory `output/build/uclibc-0.9.31.1'
> make: *** [output/build/uclibc-0.9.31.1/.stamp_built] Error 2
>
> Disable kernel headers newer than 3.6.x on avr32, and update atngw100 and
> atstk100x defconfigs to use kernel headers that avoid the uclibc build
> problem.
How much effort is it to instead fix uClibc to not break with more
recent kernel headers? It seems a little bit annoying to me that we
need to carry this !BR2_avr32 dependency for all new kernel headers
version. If the fix is one or two simple patches for uClibc 0.9.31, it
might be worthwhile.
And if it's not the case, I believe I'd prefer the dependency to be on
the uClibc version (i.e 'depends on !BR2_PACKAGE_UCLIBC_0_9_31')
instead of on the architecture, because the problem seem more related
to the uClibc version rather than the architecture.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-08 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 21:30 [Buildroot] [PATCH] avr32: disable kernel headers spdawson at gmail.com
2013-11-08 7:22 ` Thomas Petazzoni [this message]
2013-11-08 9:26 ` Simon Dawson
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=20131108082243.1a889fee@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 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.