From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: libxc/Makefile's VPATH issue Date: Mon, 9 Jun 2008 11:58:43 +0100 Message-ID: <20080609105843.GL4264@implementation.uk.xensource.com> References: <20080609104237.GH4264@implementation.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser, le Mon 09 Jun 2008 11:54:08 +0100, a écrit : > On 9/6/08 11:42, "Samuel Thibault" wrote: > > c/s 17138 introduced the use of VPATH instead of symlinks to access to > > libelf files. However, that not only provides access to .c files, but > > also to .o files. That means that if one compiles the hypervisor before > > the tools, libxenguest.a contains .o files intended to the hypervisor, > > containing references to printk, etc. and thus is unusable. > > You mean c/s 16891? Oops, yes, sorry, I was looking in my own tree. > > Is there a good reason against reverting to symlinks, or maybe another > > way to achieve the same? > > vpath %.c ../../xen/common/libelf > > Perhaps? It does work indeed. I guess we already depend on possibly GNU-only features anyway? Samuel