From owner-freebsd-questions@FreeBSD.ORG Mon May 21 06:21:30 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB3B11065672 for ; Mon, 21 May 2012 06:21:30 +0000 (UTC) (envelope-from bonomi@mail.r-bonomi.com) Received: from mail.r-bonomi.com (mx-out.r-bonomi.com [204.87.227.120]) by mx1.freebsd.org (Postfix) with ESMTP id 20AA08FC14 for ; Mon, 21 May 2012 06:21:29 +0000 (UTC) Received: (from bonomi@localhost) by mail.r-bonomi.com (8.14.4/rdb1) id q4L6NDeH009457; Mon, 21 May 2012 01:23:13 -0500 (CDT) Date: Mon, 21 May 2012 01:23:13 -0500 (CDT) From: Robert Bonomi Message-Id: <201205210623.q4L6NDeH009457@mail.r-bonomi.com> To: freebsd-questions@freebsd.org, tomdean@speakeasy.org In-Reply-To: <4FB9BAE5.5090902@speakeasy.org> Cc: Subject: Re: NanoBSD Build Failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2012 06:21:30 -0000 > From owner-freebsd-questions@freebsd.org Sun May 20 22:52:02 2012 > Date: Sun, 20 May 2012 20:47:49 -0700 > From: "Thomas D. Dean" > To: freebsd-questions@freebsd.org > Subject: Re: NanoBSD Build Failure > > On 05/20/12 20:39, Polytropon wrote: > > On Sun, 20 May 2012 19:49:49 -0700, Thomas D. Dean wrote: > >> I am attempting to rebuild nanoBSD on an AMD64 system, using the same > >> config file I used a couple years ago on a 32-bit system. > >> [...] > >> /usr/home/tomdean/nanoBSD/MYKERNEL: unknown option "I486_CPU" > > > > It seems that the amd64 sources do not understand "cpu I486_CPU". > > Compare to /sys/i386/conf/GENERIC and /sys/i386/conf/NOTES > > to the respective /sys/amd64/conf/GENERIC and /sys/amd64/conf/NOTES > > for details, especially that amd64 uses "cpu HAMMER" instead > > of "cpu I{4/5/6}86_CPU". > > > > > cd /usr/src/sys/i386/conf > > grep cpu GENERIC > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > device cpufreq > > sudo env -i /usr/sbin/config GENERIC > > Must be some problem with nanobsd.sh?? INCORRECT. You wre building in the /usr/src/sys/amd64 tree. See line 3 in the text below. Quoting 'lost context' from your original message || >>> stage 1: configuring the kernel || ------------------------------------------------------------- || cd /usr/src/sys/amd64/conf; || PATH=/usr/obj/nanobsd.TS5700//usr/src/tmp/legacy/usr/sbin:/usr/obj/nanobsd. || TS5700//usr/src/tmp/legacy/usr/bin:/usr/obj/nanobsd.TS5700//usr/src/tmp/leg || acy/usr/games:/usr/obj/nanobsd.TS5700//usr/src/tmp/usr/sbin:/usr/obj/nanobs || d.TS5700//usr/src/tmp/usr/bin:/usr/obj/nanobsd.TS5700//usr/src/tmp/usr/game || s:/sbin:/bin:/usr/sbin:/usr/bin || config -d /usr/obj/nanobsd.TS5700//usr/src/sys/MYKERNEL || /usr/home/tomdean/nanoBSD/MYKERNEL || /usr/home/tomdean/nanoBSD/MYKERNEL: unknown option "I486_CPU" And, "of course" the i486 cpu is not recognized in a '64-bit' build, since it doesn't have the 64-bit istrution set. An 'i386' kernel config is *NOT* necessarily valid for building on 'amd64'. (There are numerous config choices in i386 that are not in amd64 at all, and others that are just 'diferent'. To make up for it, amd64 has some that are not recognized in i386, either.) Vetting with a 'trained eyeball -is- required to make things work when you change between i386 and amd64 -- in either diretion. [voice of first-hand experience speaking.]