From owner-freebsd-questions Fri Oct 31 12:11:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02024 for questions-outgoing; Fri, 31 Oct 1997 12:11:13 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02011 for ; Fri, 31 Oct 1997 12:11:10 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id MAA23634; Fri, 31 Oct 1997 12:10:40 -0800 (PST) To: Michael Alwan Cc: questions@freebsd.org Subject: Re: current kernel won't build In-reply-to: Your message of "Fri, 31 Oct 1997 11:20:45 EST." Date: Fri, 31 Oct 1997 12:10:39 -0800 Message-ID: <23630.878328639@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 1. Only one mailing list at a time, please. Questions would have been enough, no need to cc -hackers. 2. If you do not subscribe to the freebsd-current mailing list then either do so or STOP running -current right now. You must read the discussions in this mailing list in order to effectively run -current and also not waste everyone's time here with -current FAQs (as your question is). 3. You need to rebuild config from -current sources if you want to be able to build the kernel. > To all: > > I just (10/31--early AM) cvsupped current, then tried to build a kernel--any > kernel--without success. One configuration problem I was able to fix: in > /i386/conf files.i386 the nxp.c driver library had the keyword "mandatory" > instead of "standard." Changing it thus did away with the error message: > > >i386/isa/npx.c standard npx device-driver > > Another mystery that causes a non-critical error is the tag in /i386/conf > Makefile.i386 for a certain version of config: > > ># Which version of config(8) is required. > >%VERSREQ= 300002 > > The command "/usr/sbin/config GENERIC" gives this warning (but creates the > kernel build directory): > > >Unknown % construct in generic makefile: %VERSREQ= 300002 > > But all of my sup's--I deleted and re-supped /src/sys 3 times--failed to buil d a > kernel with this error: > > >cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. > >-I../.. -I../../../include -DFAILSAFE -DCOMPAT_43 -DMSDOSFS -DNFS -DFFS -DIN ET > >-DKERNEL -include opt_global.h -c vers.c > >loading kernel > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > >*** Error code 1 > > > >Stop. > > I used "nm kernel" to get the symbol table from my working > kernel(970807SNAP)--no sign of the undefined symbol above: > > >f01fb5b8 b _isa_devlist > >f01f3b00 D _isa_devtab_bio > >f01f3fc8 D _isa_devtab_net > >f01f4050 D _isa_devtab_null > >f01f3e74 D _isa_devtab_tty > >f01cdbe8 T _isa_dma_acquire > > This is as far as I know how to go. > > I'll try new kernel sources later. Should I be discussing this on another > mailing list, or should I just keep trying until I get something that works? > Should I try to make world first? > > Thanks, > > Michael > ---------------------------------- > E-Mail: Michael Alwan > Date: 31-Oct-97 > Time: 11:20:45 > > This message was sent by XFMail > ----------------------------------