From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Magenheimer, Dan (HP Labs Fort Collins)" Subject: RE: (no subject) Date: Mon, 19 Sep 2005 12:20:41 -0700 Message-ID: <516F50407E01324991DD6D07B0531AD5695D6A@cacexc12.americas.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christian Limpach Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > > > Please define LINUX_ARCH in buildconfigs/Rules.mk and use=20 > that where > > > we run make ARCH=3Dxen. > > > If you can name your config file xen0_defconfig_ia64 and use > > > LINUX_ARCH for the path, then you won't need to duplicate=20 > the config > > > file code. > >=20 > > OK, I see. This cleans it up nicely. New patch attached. >=20 > You have to export LINUX_ARCH to the script. We don't want to > unconditionally polute the environment of all the commands we > run, so you'll have to add it to all the calls to mkbuildtree. I'm not sure I follow... I don't know exactly how make or bash work wrt to exporting... I didn't explicitly export LINUX_ARCH but it seems to be known by mkbuildtree and all the mk.linux's anyway. (I successfully built for x86 and ia64 with the patch.) Or are you suggesting I *not* define it in buildconfigs/Rules.mk so as to avoid polluting the environment? =20 > I think I'd prefer xen-mkbuildtree-{pre,post} as the name of=20 > the scripts > to run, but not too fussed about that... That's OK with me. If enlightenment (is that a bad word in Xen land now?) from the above requires me to re-generate the patch, I will change the names. Thanks! Dan