On Fri, May 15, 1998 at 04:11:46PM -0500, Manoj Srivastava wrote:
>       Hmm. if you use -I/usr/src/linux/include, then as far as I can
>  see; it should link with those files (as you state further, it is
>  linked to kernel-source-2.0.33). What toerh files you happen to have
>  elsewhere should not make a difference. How is sndshield getting to
>  know about 2.0.32? 
> 
>       Well, try putting in -I/usr/src/linux/include for every file
>  compiled in the tree; and see if that improves things. 
> 
>       At the last resort, you can try mkdir /usr/src/tmp; mv the
>  2.0.32 headers there, and create a symlink from kernel-source-2.0.33
>  to kernel-headers-2.0.32; compile the module, and restore things to
>  the way they were for the other 99.99% of the code that is well
>  behaved (or less dependent on kernel versions).

Thr problem with OSS/Linux is that it grep's autoconf.h to see if you have
the right configuration for module support and versioning.  This is STUPID
and WRONG, but then it's just one more example of what a shoddy piece of
crap OSS truly is.

(Get the idea this and other "features" of OSS/Linux have torked me off a
bit?)

Attachment: pgpwhLRnS7aVV.pgp
Description: PGP signature

Reply via email to