From: Paul Bender <pebender@san.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: udev, input/linux.h and cross compilation
Date: Wed, 20 Jan 2010 18:21:29 +0000 [thread overview]
Message-ID: <4B5749A9.2090005@san.rr.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
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.
I have attached a patch that determines the correct linux/include.h file
during configure. The configure change makes use of the
AX_ABOLUTE_HEADER
http://www.nongnu.org/autoconf-archive/ax_absolute_header.html, which
the patch adds to the m4.
[-- Attachment #2: udev-150-absolute_linux_input_h.patch.gz --]
[-- Type: application/gzip, Size: 1902 bytes --]
next reply other threads:[~2010-01-20 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 18:21 Paul Bender [this message]
2010-01-20 18:30 ` udev, input/linux.h and cross compilation Kay Sievers
2010-01-20 18:59 ` Paul Bender
2010-01-21 11:00 ` Martin Pitt
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=4B5749A9.2090005@san.rr.com \
--to=pebender@san.rr.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).