Re: Normal users can't build modules against kernel headers?
- To: debian-kernel@lists.debian.org
- Subject: Re: Normal users can't build modules against kernel headers?
- From: Bas van Schaik <bas@tuxes.nl>
- Date: Sat, 01 Apr 2006 15:45:45 +0200
- Message-id: <442E8409.4080804@tuxes.nl>
- In-reply-to: <44282B8B.1020407@tuxes.nl>
- References: <4421669B.90006@tuxes.nl> <20060322192305.dfd48100.dr@jones.dk> <4422B49A.20701@tuxes.nl> <20060323160924.057f7900.dr@jones.dk> <44282B8B.1020407@tuxes.nl>
>>>>Perhaps looking at existing kernel modules packaged for Debian?
>>>>
>>>>
>>>
>>>Maybe a good idea, but since the module did build before (using the
>>>upstream makefile), I thought it would be better to get the module to
>>>compile first, before trying to package it.
>>
>>
>>Still, recent official Debian kernels have made life harder for those
>>wrong assumptions above. So you might actually make life harder on
>>yourself by trying to simplify it :-)
>
>
> OK!
>
> However, the upstream developer tried a vanilla kernel 2.6.15, on which
> the module builds without any errors! So even after al the cleanup since
> 2.6.8, the module builds on a vanilla 2.6.15. The u.d. debugged some
> more (since I didn't have the time for it), and figured out that "make
> scripts" creates the missing "MARKER"-file. Can you explain to me what
> this command execution does exactly to the kernel sources/headers, and
> why it isn't done in Debian? This might solve my problem.
Anyone?
-- Bas
Reply to: