Xen devel - Nov 2012 - libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG

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

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.

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