From owner-freebsd-questions Wed Sep 27 23:22:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtppop1.gte.net (smtppop1pub.gte.net [206.46.170.20]) by hub.freebsd.org (Postfix) with ESMTP id 1042D37B424 for ; Wed, 27 Sep 2000 23:22:08 -0700 (PDT) Received: from dale2 (1Cust243.tnt2.hilo.hi.da.uu.net [63.10.189.243]) by smtppop1.gte.net with SMTP for ; id BAA3869718 Thu, 28 Sep 2000 01:17:30 -0500 (CDT) Message-ID: <000e01c02913$e0a808c0$f3bd0a3f@dale2> From: "Peter Kurpis" To: Subject: can't rebuild GENERIC Date: Wed, 27 Sep 2000 20:16:01 -1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am trying to reconfigure my kernel on version 4.1 (having installed all sources from the CDROM). I followed the instructions in the online Handbook. I had problems, so I took a step back and tried rebuilding GENERIC: cd /usr/src make buildkernel KERNEL=GENERIC 2>&1 >/tmp/make.log I attach condensed logs below. I found no similar problems in your online gnats, so I guess I must've missed something in the installation... ? Any ideas? I would appreciate any pointer in the right direction. P.S. I had to create two logs, one for stdout, and one for stderr, because 2>&1 didn't work, even though I gave root /bin/sh as the shell (using vipw ). (So sorry they're not sync'ed.) Any ideas about this problem would also be appreciated. Thanks in advance! -----[here starts stdout from make]--------------------- -------------------------------------------------------------- >>> Rebuilding kernel(s) -------------------------------------------------------------- ===> GENERIC mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/s rc/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -r -d /usr/obj/usr/src/sys/GENERIC GENERIC Don't forget to do a ``make depend'' Kernel build directory is /usr/obj/usr/src/sys/GENERIC [hundreds of healthy-looking lines deleted here] ===> wi @ -> /usr/src/sys machine -> /usr/src/sys/i386/include perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/ obj/usr/src/i386/usr/include /usr/src/sys/modules/wi/../../i386/isa/if_wi.c cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict -prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat -extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include - D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -----[here starts stderr from make]--------------------------------------- Removing old directory /usr/obj/usr/src/sys/GENERIC: Done. nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory ./aicasm: 725 instructions used /tmp/ccR28057.s: Assembler messages: /tmp/ccR28057.s:1747: Error: .space specifies non-absolute value /tmp/ccR28057.s:2473: Error: undefined symbol L0 in operation setting PTmap /tmp/ccR28057.s:2473: Error: undefined symbol PDRSHIFT in operation setting PTmap [about thirty or so more undefined symbols deleted here] /tmp/ccR28057.s:1880: Error: Subtraction of two symbols in different sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file address 38. /tmp/ccR28057.s:1881: Error: Subtraction of two symbols in different sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file address 43. [and scores more of similar messages (with different line numbers and addresses) deleted here] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message