Re: buildkernel failure [kern/kern_descrip.c]
- In reply to: Mark Johnston : "Re: buildkernel failure [kern/kern_descrip.c]"
 - Go to: [ bottom of page ] [ top of archives ] [ this month ]
 
Date: Sun, 29 Jun 2025 17:25:21 UTC
On 2025-06-29 13:13, Mark Johnston wrote: > On Sun, Jun 29, 2025 at 11:49:55AM -0400, Ian FREISLICH wrote: >> Hi >> >> I've tried with fresh source and /usr/obj cleared. >> >> /usr/src/sys/kern/kern_descrip.c:2967:53: error: too many arguments to >> function call, expected 4, have 5 >> 2967 | error = fget_unlocked(td, fd, needrightsp, flagsp, fpp); >> | ~~~~~~~~~~~~~ ^~~ >> /usr/src/sys/sys/filedesc.h:291:5: note: 'fget_unlocked' declared here >> 291 | int fget_unlocked(struct thread *td, int fd, >> | ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~ >> 292 | const cap_rights_t *needrightsp, struct file **fpp); >> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> /usr/src/sys/kern/kern_descrip.c:3144:3: error: use of undeclared identifier >> 'fsearch' >> 3144 | *fsearch = ((fp->f_flag & FSEARCH) != 0); >> | ^ >> 2 errors generated. >> *** Error code 1 >> >> Have I missed something? > > This is fixed now, thanks. Out of curiosity, why does your kernel > config not configure CAPABILITIES? Confirmed fixed. Thanks. My kernel configurations have their origins back in the mid 1990's with many updates over the years. When Capsicum was first introduced I had a slew of issues and never saw the need to add it back into config later. If it's something I really need, I'll include it but I wasn't aware that it was a mandatory thing. Ian