Odd. On my SuSE 7.0 system they're symlinks: > ls -l /usr/include/asm /usr/include/linux lrwxrwxrwx 1 root root 29 Feb 23 2001 /usr/include/asm -> ../src/linux/include/asm-s390 lrwxrwxrwx 1 root root 26 Feb 23 2001 /usr/include/linux -> ../src/linux/include/linux
I had to double-check that because the coloring scheme SuSE uses has the same color for directories as symbolic links. :( You need to make sure that /usr/include/linux/version.h matches your currently running kernel level. On my Intel 2.4.18 system, I have: #define UTS_RELEASE "2.4.18" #define LINUX_VERSION_CODE 132114 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) Yours should say #define UTS_RELEASE "2.4.17" but I have no idea what the value would be for LINUX_VERSION_CODE. You could probably get that from /usr/src/linux-2.4.17-SuSE/include/linux/version.h Mark Post -----Original Message----- From: Michael K Lambert [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 10, 2002 11:35 AM To: [EMAIL PROTECTED] Subject: Re: cpint kernel patch Hmm.../usr/include/asm and linux are directories, not symlinks. How can I ensure that the app will be compiled correctly? Michael, I don't think there is such a thing. Neale's cpint program is pretty much a standalone thing that simply uses existing kernel facilities. It doesn't make any changes to the kernel itself. What you're experiencing sounds like you have multiple versions of the kernel source on your machine, and most likely the symbolic links /usr/include/asm and /usr/include/linux are pointing to the 2.4.9 version, and not the 2.4.17 version. Mark Post
