From: Allin Cottrell <cottrell@wfu.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: Some basic questions
Date: Sat, 13 Aug 2011 03:19:48 +0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1108122313400.1765@myrtle> (raw)
In-Reply-To: <1313193543.14425.15.camel@localhost>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1392 bytes --]
On Fri, 12 Aug 2011, Frank W. Miller wrote:
> My next step is to get udev going. To that end, I've downloaded and
> studied to some extent release 172. I'm using FC12 as my build machine
> (e.g. gcc 4.4.2). This is what I think is supposed to happen, please
> correct me if I'm wrong on any of this.
>
> When I build udev, I do this:
>
> configure --enable-static
>
> This is to get the udev binaries to build without needing libraries.
> Then:
>
> make
>
> I get this:
>
> CC extras/input_id/input_id.o
> extras/input_id/input_id.c: In function ‘test_key’:
> extras/input_id/input_id.c:173: error: ‘BTN_TRIGGER_HAPPY’ undeclared
Your FC12 kernel headers are too old for building udev 172. I
believe you'll need at least 2.6.34.
> Once I get the binaries built, I'll need to install them and the config
> files in the proper places in my USB filesystem correct?
Naturally. Though you can reorganize the directory structure if you
wish via options to ./configure.
> Thanks in advance for any assistance on this. I'd really like to keep
> this as simple as possible. For example, its not clear to me what
> "extras" are and how to turn them off if they are not needed.
./configure --disable-hwdb --disable-introspection \
--disable-keymap
(and so on). See ./configure --help and
http://www.linuxfromscratch.org/lfs/view/development/chapter06/udev.html
Allin Cottrell
next prev parent reply other threads:[~2011-08-13 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 23:59 Some basic questions Frank W. Miller
2011-08-13 0:34 ` Greg KH
2011-08-13 0:50 ` Frank W. Miller
2011-08-13 3:19 ` Allin Cottrell [this message]
2011-08-13 3:33 ` Frank W. Miller
2011-08-13 18:20 ` John Lumby
2011-08-14 3:25 ` Frank W. Miller
2011-08-14 3:33 ` Frank W. Miller
2011-08-14 6:44 ` Allin Cottrell
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=alpine.DEB.2.00.1108122313400.1765@myrtle \
--to=cottrell@wfu.edu \
--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