Re: Some basic questions

["Frank W. Miller" <frankwmiller@frankwmiller.net>]

Thanks for the reply.

Correct me if I'm wrong but doesn't this essentially replace the kernel
header files in usr/include/ for the build machine with pointers to the
kernel headers for my target kernel?  I'm not sure this is a good way to
go about this.  Am I missing something?  It would be better if there was
some compile option for udev that pointed it at the desired kernel
header files, wherever they might be?

Thanks,
FM


On Sat, 2011-08-13 at 14:20 -0400, John Lumby wrote:
> To install kernel headers from your own kernel tree:
> 
>   . first build them  -
>      #  assuming current working dir is the top of your kernel build
> INSTALL_HDR_PATH=$PWD/usr make headers_install
>     should create a subdirectory path usr/include containing directories 
> such as linux video sound asm asm-generic and others
> 
>    .  then cd to /usr/include and,  for each directory in 
> <kernel>/usr/include,  first rename the one in /usr/include,  then copy 
> (or symlink it if it will always be accessible) the one under the kernel 
> tree.
> 
> On 08/12/11 23:33, Frank W. Miller wrote:
> > Thanks Allin!  Very helpful, or at least, I'll let you know...  ;)
> >
> > One question, I have the 2.6.39.2 kernel tree that I'm building for my
> > little project.  How do I point the udev build at the kernel headers in
> > that tree, e.g.:
> >
> > /home/fwmiller/roadrunner/build/linux/include
> >
> > where "linux" in this path is actually a sym link to a directory called
> > linux-2.6.29.2 in the same build/ directory?
> >
> > Also, can I just do all the --disable-* options to configure?  Is that
> > the base implementation?
> >
> > Thanks,
> > FM
> >
> >
> > On Fri, 2011-08-12 at 23:19 -0400, Allin Cottrell wrote:
> >> 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
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> >
>