mg018a0183 at blueyonder.co.uk
Sun Sep 15 04:10:42 PDT 2002
Had a similar issue recently developing device drivers for an embedded
processor. We are using LFS development hosts at work, and cross-compiling
to arm-linux. Problems arose when trying to use features in the kernel that
were enabled after building LFS, e.g. devfs support. We soon realised that
building modules was something that needed to be done against the kernel
headers (i.e. those in /usr/src/linux) and not the glibc-headers (i.e. those
is /usr/include). OK, so /usr/include contains some kernel headers, but this
is for user-space development.
Hope this helps.
"Mark Ellis" <mark.uzumati at virgin.net> wrote in message
news:20020905221843.GA643 at ElCapitan.oval.net...
> I have a minor concern about how we install the kernel headers at the
> start of chapter 6, or rather what we dont install later on. At present
> /usr/include/linux/autoconf.h is an empty file created with touch after
> copying the headers from an essentially unconfigured kernel tree.
> I just came across a missing define used by microcode_ctl, the Intel
> microcode update utility, CONFIG_X86_L1_CACHE_SHIFT, which should come
> from autoconf.h (via linux/config.h via asm/processor.h). I wouldn't
> even have noticed this, since the makefile includes
> /usr/src/linux/include, if the kernel tree top dir hadn't been changed
> to linux-$VERSION.
> Probably not a big deal since its never come up before, but for a sense
> of tidiness i propose copying autoconf.h, and while we're there
> compile.h, to /usr/include/linux after the kernel build in chapter 8.
> Any thoughts ?
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe lfs-dev' in the subject header of the message
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev