Re: 4.0-current make release failure (sysctl)

1999-02-18 Thread Doug Rabson
On Thu, 18 Feb 1999, Sheldon Hearn wrote: On Wed, 17 Feb 1999 19:12:59 EST, John W. DeBoskey wrote: Just fyi, current as of 2pm EST. ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 I get this when I set ``option

4.0-current make release failure (sysctl)

1999-02-17 Thread John W. DeBoskey
Hi, Just fyi, current as of 2pm EST. Thanks, John cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include

Re: 4.0-current make release failure (sysctl)

1999-02-17 Thread Sheldon Hearn
On Wed, 17 Feb 1999 19:12:59 EST, John W. DeBoskey wrote: Just fyi, current as of 2pm EST. ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 I get this when I set ``option NFS_NOSERVER''. If I disable the option, my kernel

Re: 4.0-current make release failure (sysctl)

1999-02-17 Thread John W. DeBoskey
Hi, I don't control the options used to build the distribution kernels during a 'make release'. Jordan is responsible for that. I don't have any problems building my local kernel since the only nfs options I have are: options NFS #Network Filesystem options