* libxc/Makefile's VPATH issue
@ 2008-06-09 10:42 Samuel Thibault
2008-06-09 10:54 ` Keir Fraser
0 siblings, 1 reply; 4+ messages in thread
From: Samuel Thibault @ 2008-06-09 10:42 UTC (permalink / raw)
To: Xen-devel
Hello,
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.
Is there a good reason against reverting to symlinks, or maybe another
way to achieve the same?
Samuel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: libxc/Makefile's VPATH issue
2008-06-09 10:42 libxc/Makefile's VPATH issue Samuel Thibault
@ 2008-06-09 10:54 ` Keir Fraser
2008-06-09 10:58 ` Samuel Thibault
0 siblings, 1 reply; 4+ messages in thread
From: Keir Fraser @ 2008-06-09 10:54 UTC (permalink / raw)
To: Samuel Thibault, Xen-devel
On 9/6/08 11:42, "Samuel Thibault" <samuel.thibault@eu.citrix.com> wrote:
> Hello,
>
> 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?
> Is there a good reason against reverting to symlinks, or maybe another
> way to achieve the same?
vpath %.c ../../xen/common/libelf
Perhaps?
-- Keir
> Samuel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: libxc/Makefile's VPATH issue
2008-06-09 10:54 ` Keir Fraser
@ 2008-06-09 10:58 ` Samuel Thibault
2008-06-09 13:14 ` John Levon
0 siblings, 1 reply; 4+ messages in thread
From: Samuel Thibault @ 2008-06-09 10:58 UTC (permalink / raw)
To: Keir Fraser; +Cc: Xen-devel
Keir Fraser, le Mon 09 Jun 2008 11:54:08 +0100, a écrit :
> On 9/6/08 11:42, "Samuel Thibault" <samuel.thibault@eu.citrix.com> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-06-09 13:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-09 10:42 libxc/Makefile's VPATH issue Samuel Thibault
2008-06-09 10:54 ` Keir Fraser
2008-06-09 10:58 ` Samuel Thibault
2008-06-09 13:14 ` John Levon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.