From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 05:53:30 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3B671065670 for ; Fri, 4 Jun 2010 05:53:30 +0000 (UTC) (envelope-from fbsdmail@dnswatch.com) Received: from fast.dnswatch.com (fast.dnswatch.com [168.103.150.11]) by mx1.freebsd.org (Postfix) with ESMTP id 7220D8FC2D for ; Fri, 4 Jun 2010 05:53:30 +0000 (UTC) Received: from www.dnswatch.com (localhost.dnswatch.com [127.0.0.1]) by fast.dnswatch.com (8.14.2/8.14.2) with ESMTP id o545rMPG059732 for ; Thu, 3 Jun 2010 22:53:29 -0700 (PDT) (envelope-from fbsdmail@dnswatch.com) Received: from udns.ultimatedns.net ([168.103.150.20]) (DNSwatchWebMail authenticated user infos) by www.dnswatch.com with HTTP; Thu, 3 Jun 2010 22:53:29 -0700 (PDT) Message-ID: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> Date: Thu, 3 Jun 2010 22:53:29 -0700 (PDT) From: fbsdmail@dnswatch.com To: freebsd-amd64@freebsd.org User-Agent: DNSwatchWebMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: who broke config(8) and why? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2010 05:53:30 -0000 Greetings, In an attempt to build an AMD64 kernel, after a buildworld session. I was greeted with a couple of unexpected surprises: make buildkernel KERNCONF=MYAMDKERN returns ERROR MYAMDKERN not found... Aparently FreeBSD only put the sys/amd64,ia64,etc... to _appear_ to support architectures other than "i386". Fine. I'll use the older method: cd sys/amd64/conf config MYAMDCONF ERROR: version of config(8) does not match kernel! config version = 600007, version required = 600009 Make sure that /usr/src/usr.sbin/config is in sync with your /usr/src/sys and install a new config binary before trying this again. If running the new config fails check your config file against the GENERIC or LINT config files for changes in config syntax, or option/device naming conventions LOOK. I already read about this in UPDIATING. I've _already_ builtworld from an 8-RELEASE CD w/cvsupped src && ports. What gives? According to UPDATING: 20100502: The config(8) command has been updated to maintain compatibility with config files from 8.0-RELEASE. You will need a new version of config to build kernels (this version can be used from 8.0-RELEASE forward). ### (this version can be used from 8.0-RELEASE forward). I'm using 8-RELEASE ### The buildworld target will generate it, ### so following the instructions in this file for updating will work glitch-free. Merely doing a make buildkernel without first doing a make buildworld ### I just DID a buildworld ### (or kernel-toolchain), or attempting to build a kernel using traidtional methods will generate a config version warning, indicating you should update. I don't get it. Why was the config(8) toolchain deliberately broken in "midstream" (the middle of a release)?! Shouldn't this/ese change(s) been made at the start of an _upcomming_ version? I suppose I have to spend another few days downloading 9-RELEASE, and tailoring it for my needs as I have already done in preparation for this build/install. _Please_ if I can avoid starting from start, all over again. Can someone tell me where I can download a pre-compiled config-toolchain. So that I can resume a biuld/install. Thank you for all your time and consideration in thia matter. --Chris