xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Roger Pau Monne <roger.pau@entel.upc.edu>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Build problems with latest xen-unstable.hg
Date: Fri, 3 Feb 2012 08:39:24 +0000	[thread overview]
Message-ID: <1328258364.13189.47.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <04d87c5a-468c-4e88-a3c6-061bbf214cf6@default>

On Fri, 2012-02-03 at 00:24 +0000, Dan Magenheimer wrote:
> I'm building xen-devel from scratch for the first time in a long
> time on a clean EL6u1 machine and running into a couple of problems.
> 
> 1) The build of tools/firmware/etherboot does a wget of a weird
>    pxe tar file that looks like it has a git hash in the filename.
>    I hacked around that (to wget the 1.0.0 version of the file).

This one is known. ixpe hasn't done a release for ages but we needed a
newer version for some bug fixes, hence we depend on a git revision now.

It is expected that the wget fails and then it falls back to generating
the tarball locally from a git checkout. I think this is pretty lame but
it is apparently a consequence of how the Makefile is structured. We
previously discussed putting a copy of that tarball on xenbits -- not
sure what happened to that plan but I have done it now and the wget
works for me (TM).

> 2) Building blktap2 complains about a missing "uuid/uuid.h".  I
>    did install the uuid and uuid-devel packages and there IS
>    a /usr/include/uuid.h but no /usr/include/uuid/uuid.h.  I found
>    I also needed to install libuuid-devel (which didn't get
>    checked in advance apparently, just uuid-devel and uuid I think).

tools/check/check_uuid_devel looks for both "uuid.h" and "uuid/uuid.h",
in that order but at least some headers (e.g. libxl_uuid.h, blktap's
ones etc) use:
	#if __linux__
	#include <uuid/uuid.h>
	#elif __BSD__
	#include <uuid.h>

It seems that on EL you can end up with uuid.h but not uuid/uuid.h which
confuses the check into succeeding where it shouldn't.

Please can you confirm that on EL6 uuid-devel
includes /usr/include/uuid.h and libuuid-devel
includes /usr/include/uuid/uuid.h

Roger, can you handle this (Linux vs. BSD?) header distinction in your
autoconf patch?

> 3) Missing texinfo package stops the build before it successfully
>    completes.  Can this be check'ed in advance?

Please can you post this log so we can find where the texinfo
requirement comes from?

Normally for these things we would patch them to only build the docs if
the required tool is present.

> Since I haven't built xen-devel in a long time, I don't know if
> these are recent problems with tip or old problems that don't
> show up on [Debian and whatever other envs other developers are
> using] but do show up on EL6.  So I thought I'd report them.

I think it's a mixture of old and new. Thanks for reporting.

Ian.

  reply	other threads:[~2012-02-03  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  0:24 Build problems with latest xen-unstable.hg Dan Magenheimer
2012-02-03  8:39 ` Ian Campbell [this message]
2012-02-03 14:03   ` Roger Pau Monné
2012-02-04 16:30   ` Dan Magenheimer

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=1328258364.13189.47.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=roger.pau@entel.upc.edu \
    --cc=xen-devel@lists.xensource.com \
    /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).