All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
	wei.liu2@citrix.com, Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] tools/configure: Check if pixman is present on the system
Date: Wed, 14 Jan 2015 12:24:18 +0000	[thread overview]
Message-ID: <1421238258.19103.247.camel@citrix.com> (raw)
In-Reply-To: <54B65D52.8020007@linaro.org>

On Wed, 2015-01-14 at 12:13 +0000, Julien Grall wrote:
> Hi Jan,
> 
> On 14/01/15 07:11, Jan Beulich wrote:
> >>>> Julien Grall <julien.grall@linaro.org> 01/13/15 7:17 PM >>>
> >> QEMU upstream requires the use of pixman. When pixman is not present the
> >> system, the configure of QEMU will fail with:
> >>
> >> ERROR: pixman not present. Your options:
> >> (1) Preferred: Install the pixman devel package (any recent
> >> distro should have packages as Xorg needs pixman too).
> >> (2) Fetch the pixman submodule, using:
> >> git submodule update --init pixman
> >>
> >> I think we can use by default the version on the system. So check it
> >> a Xen configuration time to avoid a build issue later.
> > 
> > Since qemu building isn't a required part of building the tools, is a check in
> > the tools configure process really an appropriate thing to do?
> 
> QEMU is a required part of building the tools.

Not stricty true. Pass --with-system-qemu if you wish to avoid it.

>  Any failure to build QEMU
> will make Xen tools build fail. It's reproductible with "make
> install-tools" and pixman not installed.
> 
> Regards,
> 

  reply	other threads:[~2015-01-14 12:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 18:14 [PATCH] tools/configure: Check if pixman is present on the system Julien Grall
2015-01-14  7:11 ` Jan Beulich
2015-01-14 10:39   ` Ian Campbell
2015-01-14 10:43     ` Wei Liu
2015-01-14 11:33       ` Ian Campbell
2015-01-14 11:34       ` Stefano Stabellini
2015-01-14 12:10     ` Olaf Hering
2015-01-14 12:13   ` Julien Grall
2015-01-14 12:24     ` Ian Campbell [this message]
2015-01-14 12:28       ` Julien Grall
2015-01-14 12:31         ` Ian Campbell
2015-01-14 12:32           ` Julien Grall
2015-01-14 12:38             ` Ian Campbell
2015-01-14 12:42               ` Julien Grall

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=1421238258.19103.247.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@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 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.