From: David Howells <dhowells@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dhowells@redhat.com, Rob Landley <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
linux-net@vger.kernel.org
Subject: Re: 3.10-rc1: commit ccdfcc398594 broke uClibc build.
Date: Tue, 09 Jul 2013 11:25:53 +0100 [thread overview]
Message-ID: <6325.1373365553@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAMuHMdX0aP7jm=2vAO=Mg9b-RggynRq+BosvzGfqSRtnyue4+w@mail.gmail.com>
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> The #include <linux/kernel.h> added to include/uapi/linux/netlink.h causes
> the uClibc build to go:
>
> In file included from include/linux/kernel.h:4,
> from include/linux/netlink.h:4,
> from include/linux/rtnetlink.h:5,
> from libc/inet/netlinkaccess.h:27,
> from libc/inet/if_index.c:37:
> > include/linux/sysinfo.h:8: error: expected specifier-qualifier-list before
> > '__kernel_long_t'
> > make: *** [libc/inet/if_index.o] Error 1
> >
> > If I comment out that line, it builds fine. The kernel builds (for my
> > config) either way.
Comment out which line? Line 8 of include/linux/sysinfo.h or the new #include
line?
Also, what arch are you compiling for?
David
next prev parent reply other threads:[~2013-07-09 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 4:21 3.10-rc1: commit ccdfcc398594 broke uClibc build Rob Landley
2013-07-09 8:02 ` Geert Uytterhoeven
2013-07-09 8:13 ` Geert Uytterhoeven
2013-07-09 10:25 ` David Howells [this message]
2013-07-11 23:00 ` Rob Landley
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=6325.1373365553@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=rob@landley.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