Xen devel - Feb 2012 - Build problems with latest xen-unstable.hg

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).
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).
3) Missing texinfo package stops the build before it successfully
   completes.  Can this be check''ed in advance?

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.

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.

2012/2/3 Ian Campbell <Ian.Campbell@citrix.com>:
> 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?
I've send an updated version that contains this check. The patch looks
ok in my repository, and this time I've sent it as an attachment,
let's see if that solves the whitespace problem.
>> 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.
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> > 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
Confirmed.
> > 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.
I can''t get a log on that machine anymore but will try to
remember to post one next time I install on a fresh machine.
IIRC from the distant past, the failure is harmless as
the docs build is the last thing that happens.  But maybe
the check script could indicate its absence along with an
advisory message about how to easily turn off the docs build?
(Just an idea so that newbies -- and oldies-but-newbies like
myself -- don''t get alarmed at a failed make.)

Last, I forgot one more build problem that is almost certainly
recent.  libxl_json.c failed to build, lacking a definition
for yajl_gen_no_buf.  I commented out that case in the switch
statement in libxl_json.c and the build succeeded.

Dan