Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: hal-0.5.11 fails with external toolchain/SDK
Date: Mon, 03 Nov 2008 19:55:12 -0500	[thread overview]
Message-ID: <20081104005512.GA12988@denix.org> (raw)

Hi,

New hal-0.5.11 from OpenMoko breaks builds with external-toolchain/SDK, as it 
hardcodes linux/input.h like this:

EXTRA_OECONF += "--with-linux-input-header=${STAGING_INCDIR}/linux/input.h"

In case of external-toolchain/SDK, linux-libc-headers are not installed in 
staging, but rather supplied by the SDK and referenced with extra "-I" in 
TARGET_CPPFLAGS_append, thus there is no ${STAGING_INCDIR}/linux/input.h

The above EXTRA_OECONF is used mainly for hal-right-input-h.patch (see link
below), which piggy-backs HAL's --with-linux-input-header option to use the
correct linux/input.h file in the tools/Makefile.am for proper
hal-setup-keymap-keys.txt, but breaks the build of
hald/linux/probing/probe-input.c, where it tries to include the missing
hardcoded linux/input.h

http://gitweb.openembedded.net/?p=openembedded.git;a=blob;f=packages/hal/files/hal-right-input-h.patch;hb=org.openembedded.dev

Unfortunately, the location of linux/input.h and linux-libc-headers inside the
SDK are not very standardized. I've seen them in several localtions, such as:

${SDK_PREFIX}/${TARGET_SYS}/libc/usr/include
${SDK_PREFIX}/target/usr/include

Any ideas on how to fix hal-0.5.11 with external-toolchain/SDK are welcome.

I've also submitted a ticket to track this issue - #4799

-- 
Denys



             reply	other threads:[~2008-11-04  1:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04  0:55 Denys Dmytriyenko [this message]
2008-11-04 11:13 ` hal-0.5.11 fails with external toolchain/SDK Holger Freyther
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=20081104005512.GA12988@denix.org \
    --to=denis@denix.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