Nick,
What I am trying to do though is not actually build a kernel but
simply place the linux source tree contained in the redhat source-code
rpm in the state matching the original build for a particular kernel.
Under RedHat Enterprise 3 with Linux 2.4 this was always trivial.
I would just create a symlink...
ln -s /usr/src/linux-2.4.20-31.9 /usr/src/linux
cd /usr/src/linux
cp /boot/config-2.4.20-31.9 .
make mrproper
cp config-2.4.20-31.9 .config
make oldconfig
make dep
...at this point I am able to build third party drivers like
the ati video drivers or the propriety Promise raid drivers
from source code without actually trying to build a complete
kernel (since I already have one built by RedHat).
Under Fedora Core 2 however, this process breaks down.
Unlike 3WS (which has a symlink to ../../../usr/src/linux-2.4.20-31.9
for /lib/modules/2.4.20-31.9/build), Core 2 has an actual build
directory which is only partially populated. If I try to use the
/lib/modules/2.6.6-1.406smp/build that is installed with the
kernel-smp-2.6.6-1.406 rpm, I get an error of...
cd /lib/modules/fglrx/build_mod
sh ./make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.6-1.406smp/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
What I really want to know is how RedHat intends for drivers
to be built within the framework of /lib/modules/2.6.6-1.406smp/build
seeing that it is an incomplete source tree. I assume something
else needs to be done to link the /lib/modules/2.6.6-1.406smp/build
installed by the /usr/src/linux-2.6.6-1.406 source tree installed
by kernel-sourcecode-2.6.6-1.406 but I can't quite figure out what
(short of moving aside /lib/modules/2.6.6-1.406smp/build and
replacing it with a symlink to /usr/src/linux-2.6.6-1.406.
Jack
