* Gordon Messmer ([EMAIL PROTECTED]) [020102 11:57]: > There aren't supposed to be symlinks in /usr/include/bits. If you've > modified any of those files, then you broke glibc-devel. Reinstall it.
Ok. I didn't modify any of the files, but i re-installed glibc-devel. This worked. > The symlinks are supposed to be: > /usr/include/linux -> /<linux source dir>/include/linux > /usr/include/asm -> /<linux source dir>/include/asm These were there. > Red Hat's last kernel errata included the fix for security problems in > 2.2.19, and would not have broken your compiler's environment. I haven't had the RedHat specific kernel sources since I first installed 6.2. I've always installed my own source tree and compiled my kernels from that. I just can't figure out what was different in the 2.2.20 tree. > I don't expect that programming should be a pre-req for compiling a > kernel, but if you're not going to accept the vendor-provided patches, I'd > hope you had at least a certain level of knowledge about how to replace > the package. I've followed the same proceedure for kernels since I "did my own" for 2.0.36. It's just weird that it stopped working. > I believe the HOWTO's document the symlinks required in /usr/include which > must be fixed if you remove or rename the kernel source directory. I didn't know about the file permissions before now. learn something new every day. Thanks for the glibc-devel idea. Regards, Merell -- Merell L. Matlock, Jr. Linux#: 149839 _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
