>>>>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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
