From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: hal-0.5.11 fails with external toolchain/SDK
Date: Tue, 4 Nov 2008 12:13:24 +0100 [thread overview]
Message-ID: <200811041213.25205.zecke@selfish.org> (raw)
In-Reply-To: <20081104005512.GA12988@denix.org>
On Tuesday 04 November 2008 01:55:12 Denys Dmytriyenko wrote:
> Hi,
>
> New hal-0.5.11 from OpenMoko breaks builds with external-toolchain/SDK, as
> it hardcodes linux/input.h like this:
It is Openmoko, and I did add it.
what about something among the lines of?
echo "#include <linux/input.h>" | cpp | less | grep "linux\/input.h"
z.
next prev parent reply other threads:[~2008-11-04 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 0:55 hal-0.5.11 fails with external toolchain/SDK Denys Dmytriyenko
2008-11-04 11:13 ` Holger Freyther [this message]
2008-11-04 19:48 ` Denys Dmytriyenko
2008-11-06 23:12 ` Denys Dmytriyenko
2008-11-07 9:11 ` Koen Kooi
2008-11-11 1:37 ` Denys Dmytriyenko
2008-11-14 22:24 ` Koen Kooi
2008-11-15 11:45 ` Michael 'Mickey' Lauer
2008-11-15 14:53 ` Philip Balister
2008-11-15 15:30 ` Michael 'Mickey' Lauer
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=200811041213.25205.zecke@selfish.org \
--to=zecke@selfish.org \
--cc=openembedded-devel@lists.openembedded.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