Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Jun 2010 23:14:54 -0700
From:      Garrett Cooper <yanefbsd@gmail.com>
To:        fbsdmail@dnswatch.com
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: who broke config(8) and why?
Message-ID:  <AANLkTim2DQCUG2ch4tafbnvLw_xmnFas62x0O4-xEzGd@mail.gmail.com>
In-Reply-To: <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com>
References:  <46f314811f76306b11597c30ae559621.dnswclient@www.dnswatch.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 3, 2010 at 10:53 PM,  <fbsdmail@dnswatch.com> 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

<back to regularly scheduled build program>

Done.
-Garrett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim2DQCUG2ch4tafbnvLw_xmnFas62x0O4-xEzGd>