xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: libxen build warnings due to empty XML2_CONFIG or CURL_CONFIG
Date: Thu, 22 Nov 2012 15:37:41 +0100	[thread overview]
Message-ID: <20121122143741.GA17600@aepfle.de> (raw)
In-Reply-To: <1353593466.13542.158.camel@zakaz.uk.xensource.com>

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

      reply	other threads:[~2012-11-22 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121122143741.GA17600@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).