From: Axel T. <Axel.Thimm@ATrpms.net> - 2004-05-26 07:15:52
|
On Tue, May 25, 2004 at 05:00:25PM -0500, John Morris wrote: > Hi, Axel! >=20 > You *can* use the kernel-source rpm, it's already configured for the > kernel it was built for. The question is more "for which one of the hlaf dozen shipped Red Hat kernels" ;) Red Hat is doing some tricks on using a kernel.h file defining some defines for distinguishing flavour/arch. This has proven to break too often some modules, so it has been discarded for building external modules by almost all repos. The only way to have clean headers for building external modules is to configure/prepare a kernel source tree per flavour/arch combination. You can drop all but the headers, of course. > But RedHat left out about two files needed to build a module, so I > needed to find a way to put those back in without actually writing > to the /usr/src/linux-foo tree. It turned out to be quite easy, and > my MythTV box is finally becoming somewhat functional now that the > remote is working! >=20 > As for your kernel modules, I'll move that discussion back over to the > atrpms list. >=20 > John >=20 > On Tue, 2004-05-25 at 14:50, Axel Thimm wrote: > > Hi John, > >=20 > > nice to see you here, too ;) > >=20 > > On Tue, May 25, 2004 at 12:20:41PM -0500, John Morris wrote: > > > On Tue, 2004-05-25 at 00:44, Christoph Bartelmus wrote: > > > > The SF archive *is* searchable. You have to search a bit for the se= arch =20 > > > > button, tough. > > >=20 > > > Wow, it's been staring me in the face for years now! Thanks. > > >=20 > > > > > Is there a way to build the lirc modules completely outside of the > > > > > kernel source tree, referring to the kernel sources in a read-only > > > > > fashion? > > > >=20 > > > > ./configure --with-kerneldir=3DDIR > > >=20 > > > Actually, this won't work, since 'make -C drivers' will go into the > > > kernel sources directory and do a 'make modules,' which tries to crea= te > > > some files in the kernel source tree; the kernel source tree, as I > > > mentioned, is owned by root, but the RPM builder is a normal user. > >=20 > > you cannot use the kernel-source rpm directly, you need to modify > > Makefiles and reconfigure for each target kernel. For kernel module > > rpm "production" you need to have kernel sources layed out for each > > flavour/arch combination. :( > >=20 > > That's the real PITA. :/ > >=20 > > Anyway, why reinvent the wheel, when there are lirc kernel modules > > rpms already at ATrpms? If you want to support custom kernels, one > > should first support packaging these into rpms, otherwise you will be > > producing dangling kernel module rpms (i.e. no dependencies, no > > automated, reproducable builds in chroot etc.). > >=20 > > BTW all ATrpms rpms are built as a non-root user. >=20 >=20 >=20 > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g.= =20 > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3D3149&alloc_id=3D8166&op=3Dclick --=20 Axel.Thimm at ATrpms.net |