Thorsten Kukuk wrote:
The kscd author is wrong. If somebody is including kernel header files, it is his own fault. He is, following the policy of kernel developers, not allowed to do so. And if he is doing it, it is his own responsibility to include it in a correct form. Since glibc is not involved at all here, it cannot be a glibc bug. Thanks for that feedback, but it does confuse me some, and I am hoping you could 'unconfuse' me. How is glibc not involved? I mean, and I am just trying to understand, joe@jmorris:~> rpm -qf /usr/include/linux/cdrom.h glibc-devel-2.3.4-23 joe@jmorris:~> rpm -qf /usr/include/linux/types.h glibc-devel-2.3.4-23 joe@jmorris:~> rpm -qf /usr/include/linux/byteorder/little_endian.h glibc-devel-2.3.4-23 joe@jmorris:~> rpm -qf /usr/include/asm/byteorder.h glibc-devel-2.3.4-23 All the files seemingly involved are from glibc-devel. How is glibc not involved here at all. BTW, the kscd author said and I quote, " ------- Additional Comments From thiago kde org 2005-06-07 07:21 ------- The bug is in glibc and the kernel headers. Please ask SuSE to fix them there." So he also mentioned the kernel headers, but since the files involved are from glibc-devel, I didn't understand that either. Thanks for any help. For the record, I did patch the kscd source and got it to work by basically doing what you said, by including it in the correct form, as did the OP in this thread.
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871