From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: 3.7-rc-1 Release Causing application failure for compilation
Date: Thu, 18 Oct 2012 20:39:30 +0200 [thread overview]
Message-ID: <20121018183930.GA4048@tarshish> (raw)
In-Reply-To: <CA+V-a8uj4wSz60Ov8S3MpSrUe-D5+OcpVsFjURzSEcE6VdvGGQ@mail.gmail.com>
Hello Prabhakar Lad,
On Thu, Oct 18, 2012 at 09:49:34PM +0530, Prabhakar Lad wrote:
> I have updated to 3.7-rc1 kernel version with latest head with
> commit-id 43c422eda99b894f18d1cca17bcd2401efaf7bd0
> but when I try to cross compile the Application I am getting following errors.
>
> /home/plad/ti/linus/linus/include/linux/types.h:14:26: error:
> conflicting types for 'fd_set'
> /home/plad/CodeSourcery/Sourcery_G++_Lite/bin/../arm-none-linux-gnueabi/libc/usr/include/sys/select.h:78:5:
> note: previous declaration of 'fd_set' was here
> /home/plad/ti/linus/linus/include/linux/types.h:15:25: error:
[snip]
> I use the codesourcery toolchain for cross compiling the applications
> for ARM. The same compiler is used to build the uImage for ARM, but
> when I try building the apps I see this issue. Can any help me out in
> fixing this.
It seems that you are including kernel headers directly in your userspace
code. Don't do that. Types defined in kernel headers conflict with types
defined in your toolchain's kernel headers. Instead, just use the headers that
are part of your toolchain, which in turn include kernel headers that your
toolchain was built with.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2012-10-18 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 16:19 3.7-rc-1 Release Causing application failure for compilation Prabhakar Lad
2012-10-18 18:39 ` Baruch Siach [this message]
2012-10-22 5:09 ` Prabhakar Lad
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=20121018183930.GA4048@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).