[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0

On Tue, 2016-02-09 at 17:53 +0100, Luis R. Rodriguez wrote:
> > > === PCI passthrough capability has been enabled ===
> > > Â CCÂÂÂÂqemu-nbd.o
> > > In file included from ./xen-config-host.h:19:0,
> > > ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfrom ./config-host.h:18,
> > > ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfrom ./qemu-common.h:33,
> > > ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfrom qemu-nbd.c:20:
> > > /usr/local/include/xenctrl.h:1229:9: error: unknown type name 
> > > âxen_sysctl_topologyinfo_tâ
> > > Âtypedef xen_sysctl_topologyinfo_t xc_topologyinfo_t;
> > 
> > If this was building from xen.git then the problem would appear to be that
> > it is picking up headers from /usr/local instead of the ones from in tree
> > (i.e. the libraries its just built).
> Hrm, I don't typically build things which are custom other than Xen on this
> system. Is this an issue ? Should we be picking up the local Xen directory for
> header stuff ? Could this perhaps be a dependency issue with a make install
> needing headers first prior to building another package? I really don't
> build custom stuff here other than Xen, and I never use a custom prefix.

The xen.git build system has been arranged such that the presence of xen
headers anywhere else (including in /usr/local) shouldn't be an issue,
since things should always be picked up from xen.git first.

However, maybe you are building qemu independently outside of the Xen build
system, it's not entirely clear. If that is the case then you do of course
need to "make install" Xen first (and/or do things with CFLAGS/LDFLAGS so
the QEMU build can find the Xen bits).

That uncertainty is why I asked:

> > However more information about your build environment and commands would be
> > needed to say for sure.

With which I was hoping you would describe clearly which repositories you
were building and which commands you were running in each.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.