GRSec not compiling on Red Hat ES3

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

GRSec not compiling on Red Hat ES3

Postby amadei » Tue Oct 05, 2004 4:14 pm

Building a kernel on Red Hat is somewhat new to me... I prefer Slack. Anyway, I am building a 2.6.7 kernel (for the first time, as well), and I applied the security patches 2.6.7 needed... then GrSec 2.0.1. I configured the GRSec stuff very much like I used to under Slack with a 2.4.x kernel, but when the compile started, I got this error... and I'm kinda stumped why.

kernel/sysctl.c:163: `PAX_ASLR' undeclared here (not in a function)
kernel/sysctl.c:163: initializer element is not constant
kernel/sysctl.c:163: (near initialization for `pax_table[0].ctl_name')
kernel/sysctl.c:169: initializer element is not constant
kernel/sysctl.c:169: (near initialization for `pax_table[0]')
kernel/sysctl.c:173: `PAX_SOFTMODE' undeclared here (not in a function)
kernel/sysctl.c:173: initializer element is not constant
kernel/sysctl.c:173: (near initialization for `pax_table[1].ctl_name')
kernel/sysctl.c:179: initializer element is not constant
kernel/sysctl.c:179: (near initialization for `pax_table[1]')
kernel/sysctl.c:964: `KERN_PAX' undeclared here (not in a function)
kernel/sysctl.c:964: initializer element is not constant
kernel/sysctl.c:964: (near initialization for `fs_table[12].ctl_name')
kernel/sysctl.c:968: initializer element is not constant
kernel/sysctl.c:968: (near initialization for `fs_table[12]')
kernel/sysctl.c:971: initializer element is not constant
kernel/sysctl.c:971: (near initialization for `fs_table[13]')
make[1]: *** [kernel/sysctl.o] Error 1
make: *** [kernel] Error 2

I probably did something stupid, so please enlighten me.

----Steve

CISSP for hire... Resume: http://www.amadei.com/resume.doc
amadei
 
Posts: 11
Joined: Tue Mar 26, 2002 1:14 am

Postby spender » Tue Oct 12, 2004 7:18 am

A hunk of the patch failed in include/linux/sysctl.h probably and you didn't correct it. If you're ever applying other patches to a kernel in addition to grsec, it's always prudent to check for rejects by issuing the command:
find -name "*.rej"
from the base of the kernel source tree.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm


Return to grsecurity support