* libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG
@ 2012-11-22 13:56 Olaf Hering
2012-11-22 14:11 ` Ian Campbell
0 siblings, 1 reply; 3+ messages in thread
From: Olaf Hering @ 2012-11-22 13:56 UTC (permalink / raw)
To: xen-devel
If XML2_CONFIG or CURL_CONFIG is empty, make in tools/libxen will print
an error 'make[3]: --cflags: Command not found'. I think a simple way to
fix this is:
shell test -n "$(XML2_CONFIG)" ; then $(XML2_CONFIG) --cflags ; fi
Olaf
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG
2012-11-22 13:56 libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG Olaf Hering
@ 2012-11-22 14:11 ` Ian Campbell
2012-11-22 14:37 ` Olaf Hering
0 siblings, 1 reply; 3+ messages in thread
From: Ian Campbell @ 2012-11-22 14:11 UTC (permalink / raw)
To: Olaf Hering; +Cc: xen-devel@lists.xen.org
On Thu, 2012-11-22 at 13:56 +0000, Olaf Hering wrote:
> If XML2_CONFIG or CURL_CONFIG is empty, make in tools/libxen will print
> an error 'make[3]: --cflags: Command not found'. I think a simple way to
> fix this is:
> shell test -n "$(XML2_CONFIG)" ; then $(XML2_CONFIG) --cflags ; fi
XML2_CONFIG/CURL_CONFIG comes from configure.ac so if it is empty things
should be arranged such that either configure fails or libxen isn't
built, probably the second options.
Does anyone even use libxen? AFAIK it targets the incomplete 0.X version
of the XenAPI which xend half implements.
Ian.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG
2012-11-22 14:11 ` Ian Campbell
@ 2012-11-22 14:37 ` Olaf Hering
0 siblings, 0 replies; 3+ messages in thread
From: Olaf Hering @ 2012-11-22 14:37 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel@lists.xen.org
On Thu, Nov 22, Ian Campbell wrote:
> On Thu, 2012-11-22 at 13:56 +0000, Olaf Hering wrote:
> > If XML2_CONFIG or CURL_CONFIG is empty, make in tools/libxen will print
> > an error 'make[3]: --cflags: Command not found'. I think a simple way to
> > fix this is:
> > shell test -n "$(XML2_CONFIG)" ; then $(XML2_CONFIG) --cflags ; fi
>
> XML2_CONFIG/CURL_CONFIG comes from configure.ac so if it is empty things
> should be arranged such that either configure fails or libxen isn't
> built, probably the second options.
Now I see, configure is called with --enable-xenapi.
For some reason the linking does not fail due to missing libxml*.so.
curl is only required for the test programs.
> Does anyone even use libxen? AFAIK it targets the incomplete 0.X version
> of the XenAPI which xend half implements.
I dont know.
Olaf
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-11-22 14:37 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-22 13:56 libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG Olaf Hering
2012-11-22 14:11 ` Ian Campbell
2012-11-22 14:37 ` Olaf Hering
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).