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

["Luis R. Rodriguez" <mcgrof@xxxxxxxx>]

On Tue, Feb 09, 2016 at 04:39:20PM +0000, Ian Campbell wrote:
> On Tue, 2016-02-09 at 17:30 +0100, Luis R. Rodriguez wrote:
> > On Tue, Feb 09, 2016 at 04:22:01PM +0000, Ian Campbell wrote:
> > > On Tue, 2016-02-09 at 17:09 +0100, Luis R. Rodriguez wrote:
> > > > The realization that compilation is not working for some modern
> > > > tools, in particular for OpenSUSE factory for a long time without
> > > > it being addressed is a bit concerning.
> > > 
> > > I don't know what OpenSUSE factory is building but Xen 4.6.0 built in
> > > Debian just fine using gcc 5 
> > 
> > Odd, I have a debian testing box I also build against and I also have
> > issues
> > building there. The latest ones now:
> > 
> > The error log from compiling the libSDL test is:
> > /tmp/qemu-conf--5604-.c:1:17: fatal error: SDL.h: No such file or directory
> 
> Missing dev package, not a gcc 5 vs 6 issue.

Its odd considering I had been building Xen for a long time without such dev
packages. Perhaps we don't propagate --disable-gfx-check for on
tools/qemu-xen-traditional-dir if no such sdl dev packages is found.

Should it ? All I know is this used to build.

The configure error there is:

ERROR: QEMU requires SDL or Cocoa for graphical output
To build QEMU without graphical output configure with --disable-gfx-check
Note that this will disable all output from the virtual graphics card
except through VNC or curses.

> > compilation terminated.
> > qemu successfuly configured for Xen qemu-dm build
> > make[3]: Entering directory '/home/mcgrof/devel/xen/tools/qemu-xen-
> > traditional-dir-remote'
> > 
> > And then:
> > 
> > === 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.

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

Debian testing. The only thing I do a custom install with is Xen. So if it
has old headers it might be from previous manual installs.

  Luis

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel