* Gordon Messmer ([EMAIL PROTECTED]) [020102 01:25]: > On Tue, 1 Jan 2002, Merell L. Matlock, Jr. wrote: > > > A typical error: > > > > /usr/include/bits/sigcontext.h:28 (asm/sigcontext.h) No such file or > > directory. > > > > Since I am not a programmer, I have no clue as to what this means. > > /usr/include/linux and /usr/include/asm are usually symlinks to your > kernel headers to your Linux source directory. Check them. They're > likely broken now.
I put symlinks in both /usr/include and /usr/include/bits. No joy... > If you're not a programmer, why are you compiling a kernel? Not to > be derogatory or anything, but was there a specific problem you were > trying to fix? Hmmmm....wasn't aware that knowing programming was a pre-requisite for compiling a kernel/user programs. I've been compiling stuff just fine since RH5.0. As far as a specific problem, yeah, security issues are a problem for me. When they are brought up, I usually try to upgrade/patch. > Have you read the HOWTO's related to kernel compiling? The kernel compiled just fine. It's other programs (slrn, mutt, etc) that will not compile now. -- Merell L. Matlock, Jr. Linux#: 149839 _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
