search for: hypervisor_amd64_amd64

...g a setup preferring glibc and gcc-defaults from experimental: ... gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -DNDEBUG -I/tmp/buildd/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/include -I/tmp/buildd/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-generic -I/tmp/buildd/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs -DHAVE_GAS_VMX -DHAVE...

...eloc.o objcopy -O binary reloc.lnk reloc.bin (od -v -t x reloc.bin | tr -s ' ' | awk 'NR > 1 {print s} {s=$0}' | \ sed 's/ /,0x/g' | sed 's/,0x$//' | sed 's/^[0-9]*,/ .long /') >reloc.S make[7]: Leaving directory '/??PKGBUILDDIR??/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/boot' gcc -D__ASSEMBLY__ -include /??PKGBUILDDIR??/debian/build/build-hypervisor_amd64_amd64/xen/include/xen/config.h -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -...

...nu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 -fomit-frame-pointer -nostdinc -fno-builtin -fno-common -Werror -Wredundant-decls -Wno-pointer-arith -pipe -g -D__XEN__ -include /<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/include/xen/config.h '-D__OBJECT_FILE__="runtime.o"' -Wa,--strip-local-absolute -MMD -MF ./.runtime.o.d -I/<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/include -I/<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm...

...ld: gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -DNDEBUG -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/tmp/xen-4.2.1/debian/build/build-hypervisor_amd64_amd64/xen/include -I/tmp/xen-4.2.1/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-generic -I/tmp/xen-4.2.1/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs -mno-red-zone -mno-sse -fpic -fno-a...

...IN + symbols_offsets[n]) ^ symbols.c:136:13: note: in expansion of macro ?symbols_address? if (symbols_address(i) > symbols_address(low)) { ^ cc1: all warnings being treated as errors /xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk:165: recipe for target 'symbols.o' failed make[6]: *** [symbols.o] Error 1 make[6]: Leaving directory '/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/common' /xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk:153: recipe for target '/xen-4.4...

Package: xen Version: 4.1.0-3 Severity: important Tags: wheezy sid User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures,

...truct_gnttab_dump_table__dom' at file scope compat/grant_table.c:29:1: error: variably modified '__checkFstruct_gnttab_dump_table__status' at file scope make[6]: *** [grant_table.o] Error 1 make[6]: Leaving directory `/build/user-xen-3_3.4.2-2-amd64-H2KV0w/xen-3-3.4.2/debian/build/build-hypervisor_amd64_amd64/xen/common' make[5]: *** [/build/user-xen-3_3.4.2-2-amd64-H2KV0w/xen-3-3.4.2/debian/build/build-hypervisor_amd64_amd64/xen/common/built_in.o] Error 2 make[5]: Leaving directory `/build/user-xen-3_3.4.2-2-amd64-H2KV0w/xen-3-3.4.2/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86' make[4...

...ope compat/grant_table.c:29:1: error: variably modified '__checkFstruct_gnttab_dump_table__status' at file scope make[6]: *** [grant_table.o] Error 1 make[6]: Leaving directory `/build/user-xen-unstable_3.3-unstable+hg17961-1-amd64-zX009M/xen-unstable-3.3-unstable+hg17961/debian/build/build-hypervisor_amd64_amd64/xen/common' make[5]: *** [/build/user-xen-unstable_3.3-unstable+hg17961-1-amd64-zX009M/xen-unstable-3.3-unstable+hg17961/debian/build/build-hypervisor_amd64_amd64/xen/common/built_in.o] Error 2 make[5]: Leaving directory `/build/user-xen-unstable_3.3-unstable+hg17961-1-amd64-zX009M/xen-unstable...

...mu2 Severity: serious This package fails to build in unstable: > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux ... > mkdir -p compat > grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \ > python /<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/tools/compat-build-source.py >compat/grant_table.c.new > mv -f compat/grant_table.c.new compat/grant_table.c > gcc -E -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typ...

...is package fails to build in unstable: > >> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux > ... >> mkdir -p compat >> grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \ >> python /<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/tools/compat-build-source.py >compat/grant_table.c.new >> mv -f compat/grant_table.c.new compat/grant_table.c >> gcc -E -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-l...

...(Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux > ... > > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs???-DNDEBUG -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include??-I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-generic -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs -DHAVE_GAS_VMX -DHAVE_GAS_EPT -DHAVE_GAS_FSGS...

...sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -DNDEBUG -I/<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/include -I/<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-generic -I/<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs -DHAVE_...

...our usual apt-sourcing and build-depping, but add the pep target to debian/rules: (I put it right underneath include debian/rules.defs) DEB_CONFIGURE_EXTRA_FLAGS += --enable-targets=x86_64-pep then do your usual binary run to produce the files needed. You?ll find xen.efi in ./debian/build/build-hypervisor_amd64_amd64/xen/xen.efi 2. Allow UEFI to find your xen.efi UEFI uses your ESP to launch the efi binaries, so that?s where it needs to go. Simply put (not symlink) xen.efi in /boot/efi/EFI/debian/ 3. Configure dom0 booting In order for Xen to boot your dom0, you?ll have to do two things: - Get the kernel a...

...pping, but add the pep target to debian/rules: > > (I put it right underneath include debian/rules.defs) > > DEB_CONFIGURE_EXTRA_FLAGS += --enable-targets=x86_64-pep > > then do your usual binary run to produce the files needed. > You?ll find xen.efi in ./debian/build/build-hypervisor_amd64_amd64/xen/xen.efi > > 2. Allow UEFI to find your xen.efi > > UEFI uses your ESP to launch the efi binaries, so that?s where it needs to go. > Simply put (not symlink) xen.efi in /boot/efi/EFI/debian/ > > 3. Configure dom0 booting > > In order for Xen to boot your dom0, you?...

...ntain the necessary support. > --enable-targets=x86_64-pep is actually something which needs to be > passed to the *binutils* configure, and this is done on Debian. > > > then do your usual binary run to produce the files needed. > > You?ll find xen.efi in ./debian/build/build-hypervisor_amd64_amd64/xen/xen.efi > > It turns out that the Debian build is already building xen.efi today, it > just isn't putting it in the package! > > I think it would be sensible to pickup this binary for inclusion, either > in the existing xen-hypervisor package or into a new EFI package. &...

...8bcabab6e0bbd929f69b613e167edfd # Parent 4b0692880dfa557d4e1537c7a58c412c1286a416 xen: ioapic: avoid gcc 4.6 warnings about uninitialised variables gcc 4.6 complains: io_apic.c: In function 'restore_IO_APIC_setup': /build/user-xen_4.1.0-3-amd64-zSon7K/xen-4.1.0/debian/build/build-hypervisor_amd64_amd64/xen/include/asm/io_apic.h:150:26: error: '*((void *)&entry+4)' may be used uninitialized in this function [-Werror=uninitialized] io_apic.c:221:32: note: '*((void *)&entry+4)' was declared here /build/user-xen_4.1.0-3-amd64-zSon7K/xen-4.1.0/debian/build/build...

...8bcabab6e0bbd929f69b613e167edfd # Parent 4b0692880dfa557d4e1537c7a58c412c1286a416 xen: ioapic: avoid gcc 4.6 warnings about uninitialised variables gcc 4.6 complains: io_apic.c: In function 'restore_IO_APIC_setup': /build/user-xen_4.1.0-3-amd64-zSon7K/xen-4.1.0/debian/build/build-hypervisor_amd64_amd64/xen/include/asm/io_apic.h:150:26: error: '*((void *)&entry+4)' may be used uninitialized in this function [-Werror=uninitialized] io_apic.c:221:32: note: '*((void *)&entry+4)' was declared here /build/user-xen_4.1.0-3-amd64-zSon7K/xen-4.1.0/debian/build/build...

On Sun, 2014-09-07 at 00:02 +0200, John Keates wrote: > How do I assist with getting this in for Jessie? > > I have this working in a fairly easy setup, it basically only requires > the pep target to be on for debian?s Xen package, What is "pep"? > and a tiny bit of infrastructure to get xen.efi, vmlinuz, an initrd > and a xen.cfg on to the ESP partition and letting