On Wed, 29 Jul 2015 at 17:53 Thomas Leonard <[email protected]> wrote:
> > This is now done. There is now a separate "minios-xen" opam package > (and mirage-xen-minios now just depends on that). You should now be > able to pin my minios-xen Git repository to test the latest version, > just as for any other library, e.g. > > opam pin add minios-xen https://github.com/talex5/mini-os.git > > As part of this, I've also made a new Mini-OS release (0.7): > > * First release from the separate Mini-OS repository > * x86: Don't print a stack trace on exit > * printf now supports %z > * Don't use -fno-tree-loop-distribute-patterns if the compiler doesn't > support it (@hannesm) > * Remove "Cannot handle page request order %d!" warning - just return > NULL on OOM > * Add opam file for easier installation > On the normal Trusty cubieboard2 image I can install minios-xen fine, but on Vivid I get an error: $ opam install minios-xen [ERROR] The compilation of minios-xen failed at "make debug=n". ... ### stderr ### # dtc/libfdt/fdt_ro.c:453:6: error: ‘nodedepth’ may be used uninitialized in this function [-Werror=maybe-uninitialized] # [...] # /home/mirage/.opam/4.02.1/build/minios-xen.0.7/include/libfdt.h: In function ‘fdt_parent_offset’: # dtc/libfdt/fdt_ro.c:468:9: error: ‘nodedepth’ may be used uninitialized in this function [-Werror=maybe-uninitialized] # return fdt_supernode_atdepth_offset(fdt, nodeoffset, # ^ # dtc/libfdt/fdt_ro.c:453:6: note: ‘nodedepth’ was declared here # int nodedepth; # ^ # cc1: all warnings being treated as errors # make: *** [/home/mirage/.opam/4.02.1/build/minios-xen.0.7/dtc/libfdt/fdt_ro.o] Error 1 mirage-xen-minios.0.7.0 was OK because of: https://github.com/talex5/xen/commit/804d40b4fe00d68e1be3160f8bcc0d94f3d4edf0 I'm guessing that the difference in this image is that it has GCC-4.9.2 instead of 4.8.x, but I'm not certain. Luke
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
