Xen project Mailing List

Re: [Xen-devel] Bug in 2.0.6 "buildconfigs" ?

From: Christian Limpach <christian.limpach@xxxxxxxxx>

Date: Tue, 24 May 2005 00:59:20 +0100

Delivery-date: Mon, 23 May 2005 23:58:58 +0000

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hip6vWC4qjEa3G1ANcuNW8Zz/CdZTfGOqlg9KGeIitrAIrsG3V7xWEt8ZFBqin5j3eN72tydmH06NT0aetjvRxdv9ZiwgtnWveUKsigcpr1lBpc/yWY1vcc0qggL3G2oG1mq/YztPjiuPWpS+MQxBeulFixHBFJ8JjiyFhNah5Y=

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 5/23/05, tdc <tdc@xxxxxxxxxxxx> 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. > > 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 = 2 > PATCHLEVEL = 6 > SUBLEVEL = 11 > EXTRAVERSION = .10$(XENGUEST) > XENGUEST = -xen0 > NAME=Woozy Beaver > --- That's ok, EXTRAVERSION only gets expanded when it's used -- which is after XENGUEST is defined. christian _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.