From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: Bug in 2.0.6 "buildconfigs" ? Date: Tue, 24 May 2005 00:59:20 +0100 Message-ID: <3d8eece2050523165972fb3383@mail.gmail.com> References: <4291D9E6.50109@phreaker.net> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4291D9E6.50109@phreaker.net> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: tdc Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 5/23/05, tdc wrote: > I think there is a bug in mk.linux-2.6-* scripts which leads to always > using xenX-defconfigs and ignoring configs in dist/install/boot. >=20 > On line 34 in mk.linux-2.6-* you check for file: > $(DESTDIR)/boot/config-$(LINUX_VER)$$CONFIG_VERSION > this evals to filename "config-2.6.11.10$(XENGUEST)", which is obviously > wrong. Yeah, I've fixed this now in 2.0-testing and unstable. > Makefiles in toplevel kernel trees does have the same error in it > (these are set on line 30 in mk.linux-2.6.*) > Makefile (for xen0) then starts with: > --- > VERSION =3D 2 > PATCHLEVEL =3D 6 > SUBLEVEL =3D 11 > EXTRAVERSION =3D .10$(XENGUEST) > XENGUEST =3D -xen0 > NAME=3DWoozy Beaver > --- That's ok, EXTRAVERSION only gets expanded when it's used -- which is after XENGUEST is defined. christian