From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev, input/linux.h and cross compilation
Date: Thu, 21 Jan 2010 11:00:33 +0000 [thread overview]
Message-ID: <20100121110033.GB2351@piware.de> (raw)
In-Reply-To: <4B5749A9.2090005@san.rr.com>
Hello,
Paul Bender [2010-01-20 10:21 -0800]:
> The top level Makefile.am hard codes /usr/include/linux/input.h for
> use in the generation of extras/keymap/keys.txt. Such hard coding
> does not work when cross compiling as the linux/input.h file that
> should be used is the cross environment's linux/include.h not
> /usr/include/linux/input.h.
Could we use
$ echo '#include <linux/input.h>' | cpp -M | xargs -n1 | grep linux/input.h
/usr/include/linux/input.h
to figure out the real path?
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
next prev parent reply other threads:[~2010-01-21 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 18:21 udev, input/linux.h and cross compilation Paul Bender
2010-01-20 18:30 ` Kay Sievers
2010-01-20 18:59 ` Paul Bender
2010-01-21 11:00 ` Martin Pitt [this message]
2010-01-22 1:29 ` Paul Bender
2010-01-22 14:02 ` Dan Nicholson
2010-01-24 19:23 ` Kay Sievers
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=20100121110033.GB2351@piware.de \
--to=martin.pitt@ubuntu.com \
--cc=linux-hotplug@vger.kernel.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).