I'm not sure if this is a bug/missconfiguration issue but I've just run across it after an upgrade to 2.2.14. After moving from kernel 2.2.13 to 2.2.14 I tried to recompile something else and it couldn't find the /usr/include/asm stuff. This is reported in bug #7574. (symlink: /usr/include/asm is pointing at /usr/src/linux/include/asm rather than asm-i386) Looking at the other links in /usr/include that I understand should be symlinks to kernel includes I find that /usr/include/linux is a symlink pointing to the right target but /usr/include/scsi is not. /usr/include/scsi is a directory containing 2 header files and it belongs to the glibc-devel-2.1.2-11 pkg rather than being a symlink to /usr/src/linux/include/scsi. I may be completely mixed up (I'm not a linux guru.) but shouldn't /usr/include/asm,linux,scsi be symlinks to the corresponding kernel includes? Why isn't /usr/include/scsi a symlink to the kernel includes? (belonging to the kernel-headers pkg) I would like to just delete /usr/include/scsi and recreate it as a symlink to the kernel includes but I'm not sure if I'll break something important by doing so. I wonder because the kernel scsi include dir contains the files 'scsi.h, scsi_ioctl.h, scsicam.h, and sg.h' where the glibc-devel supplied dir contains only 2 headers 'scsi.h and sg.h'. System is RH 6.1 w/relevant errata updates on a PII333. Yes I have /usr/src/linux as a symlink pointing at the correct current kernel src. ;)
This is intentional; glibc-devel contains some generic not-kernel-specific scsi headers.