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

On Wed, 2015-01-14 at 07:11 +0000, 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?

It's quite annoying as a user to have configure appear to succeed and
then the build to fail due to a missing dependency (whether in a 3rd
party component or not).

We could make this check conditional on --with-qemu-system not being
given, but given the library is readily available I don't think its the
end of the world to have a potentially unnecessary check.

A far more heavy weight (but probably better) solution would be to
arrange for the clone (and necessary downloads) + submodule configure to
happen at configure rather than build time. That's a much bigger job
though and I wouldn't expect anyone to take that on unless they are
super duper keen.

Ian.

  reply	other threads:[~2015-01-14 10:39 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 [this message]
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
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=1421231985.19103.200.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.