Date: Sat, 6 Jan 1996 04:38:29 -0500 (EST) From: "Marc G. Fournier" <scrappy@ki.net> To: current@freebsd.org Subject: Problem compiling kernel: Jan 5th sources Message-ID: <Pine.BSF.3.91.960106043040.10517A-100000@hub.org>
next in thread | raw e-mail | index | archive | help
Hi... Last night, I recompiled the kernel on my -current machine, after which I realized that I forgot to run sup first :( So, I sup'd in the current newest sources, and performed a 'make clean; make depend; make' to make the kernel. Oh, and, I did a 'config -ng <configfile>', just in case something changed there. Now, when I compile, I'm getting: freebsd# make cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-\ externs -Wstrict-prototypes -Wmissing-prototypes -Winline -g -nostdinc -I. \ -I../.. -I../../sys -I../../../include -DI386_CPU -DXSERVER -DPCVT_FREEBSD=210 \ -DUCONSOLE -DBOUNCE_BUFFERS -DSCSI_DELAY=15 -DCOMPAT_43 -DDEVFS -DMSDOSFS \ -DNFS -DFFS -DINET -DDODUMP -DQUOTA -DOPEN_MAX=128 -DCHILD_MAX=128 -DKERNEL \ ../../kern/sysv_msg.c ../../kern/sysv_msg.c:50: `msgctl' undeclared here (not in a function) ../../kern/sysv_msg.c:50: initializer element for `msgcalls[0]' is not constant ../../kern/sysv_msg.c:50: `msgget' undeclared here (not in a function) ../../kern/sysv_msg.c:50: initializer element for `msgcalls[1]' is not constant ../../kern/sysv_msg.c:51: `msgsnd' undeclared here (not in a function) ../../kern/sysv_msg.c:51: initializer element for `msgcalls[2]' is not constant ../../kern/sysv_msg.c:52: `msgrcv' undeclared here (not in a function) ../../kern/sysv_msg.c:52: initializer element for `msgcalls[3]' is not constant ../../kern/sysv_msg.c:124: warning: function declaration isn't a prototype And a few others... I noticed all the stuff about a 'new options', but, to be honest, don't know what changed in that, and if it affects me...sorry. I've looked in the code itself, to see if maybe there is an option that I should have enabled for that section of code, or above it in the way of include files, but there is nothing that looks out to me. The funny thing is...that file is dated Dec 15th, so there hasn't been any recent changes to it that I can tell, yet *now* it breaks...? The config file that I'm using has not been changed in several weeks, but, again, there doesn't seem to be anything in that file that would be affected by my config file in a way that would cause those errors. Anyone else see this? Thanks.. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960106043040.10517A-100000>