From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 4 06:14:56 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 EAD271065677 for ; Fri, 4 Jun 2010 06:14:55 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9EF668FC19 for ; Fri, 4 Jun 2010 06:14:55 +0000 (UTC) Received: by vws19 with SMTP id 19so667151vws.13 for ; Thu, 03 Jun 2010 23:14:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6oPUTygsbbgQvQyWCWw0R3sHO1rVYUtRTJ3QI94G21s=; b=xlIt9BUvAChMp+OU4YERs0iWpW1bYCH+6zr1dtUn/z23EFH2Cpq0+fX/PNbC41g37f I+f68A8F3KRr5AqoZwkTYzW2OWSBOzz5++6C9gqxI7mEepv3TZTIhKN6KR+UuaaaGZ7b otkwaXss3KbZRU3mneTuTrbH8ar8P6V1hiVRo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iIitQkTEFfgeSuzrB6880iTDl81ksefA7VyVQM7uQmvxXpvNI2AEKaAtwsOdd3q/o3 zpTw06UWu+skT7ua5nMUSiPDXiKm83O8ckLlF92K/q0k4x4+wWCj5b9nD+KYaorkHOlk 5DIl2bgs276nTqxmXqSVO+4onW90+vXr5QUUo= MIME-Version: 1.0 Received: by 10.224.78.142 with SMTP id l14mr5593613qak.174.1275632094067; Thu, 03 Jun 2010 23:14:54 -0700 (PDT) Received: by 10.229.233.74 with HTTP; Thu, 3 Jun 2010 23:14:54 -0700 (PDT) In-Reply-To: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> References: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com> Date: Thu, 3 Jun 2010 23:14:54 -0700 Message-ID: From: Garrett Cooper To: fbsdmail@dnswatch.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@freebsd.org Subject: Re: 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 06:14:56 -0000 On Thu, Jun 3, 2010 at 10:53 PM, wrote: > Greetings, > =A0In an attempt to build an AMD64 kernel, after a buildworld session. I = was > greeted with a couple of unexpected surprises: > make buildkernel KERNCONF=3DMYAMDKERN returns ERROR MYAMDKERN not found..= . > > Aparently FreeBSD only put the sys/amd64,ia64,etc... to _appear_ to suppo= rt > 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 =3D 600007, version required =3D 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: > =A0 =A0 =A0 =A0The config(8) command has been updated to maintain compati= bility > =A0 =A0 =A0 =A0with config files from 8.0-RELEASE. =A0You will need a new= version > =A0 =A0 =A0 =A0of config to build kernels (this version can be used from = 8.0-RELEASE > =A0 =A0 =A0 =A0forward). > ### > (this version can be used from 8.0-RELEASE forward). > I'm using 8-RELEASE > ### > =A0The buildworld target will generate it, > ### > =A0so following > =A0 =A0 =A0 =A0the instructions in this file for updating will work glitc= h-free. > =A0 =A0 =A0 =A0Merely doing a make buildkernel without first doing a make= buildworld > ### > I just DID a buildworld > ### > =A0 =A0 =A0 =A0(or kernel-toolchain), or attempting to build a kernel usi= ng > =A0 =A0 =A0 =A0traidtional methods will generate a config version warning= , indicating > =A0 =A0 =A0 =A0you 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. make -C usr.sbin/config all install Done. -Garrett