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

Bug#778181: marked as done (xen: ftbfs with GCC-5)



Your message dated Fri, 13 Mar 2015 14:19:42 +0000
with message-id <[🔎] 1426256382.32572.155.camel@debian.org>
and subject line Re: [Pkg-xen-devel] Bug#778181:  Bug#778181: xen: ftbfs with GCC-5
has caused the Debian Bug report #778181,
regarding xen: ftbfs with GCC-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
778181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778181
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:xen
Version: 4.4.1-6
Severity: normal
Tags: sid stretch
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/xen_4.4.1-6_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
objdump -h reloc.o | sed -n '/[0-9]/{s,00*,0,g;p}' |\
	while read idx name sz rest; do \
		case "$name" in \
		.data|.data.*|.rodata|.rodata.*|.bss|.bss.*) \
			test $sz != 0 || continue; \
			echo "Error: non-empty $name: 0x$sz" >&2; \
			exit $(expr $idx + 1);; \
		esac; \
	done
ld -melf_i386 -N -Ttext 0 -o reloc.lnk reloc.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 -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_GAS_VMX -DHAVE_GAS_EPT -DHAVE_GAS_FSGSBASE -mno-red-zone -mno-sse -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -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 -nostdinc -DHAS_ACPI -DHAS_GDBSX -DHAS_PASSTHROUGH -DHAS_PCI -
 DHAS_IOPORTS -MMD -MF .head.o.d -c head.S -o head.o
ld    -melf_x86_64  -r -o built_in.o head.o
make[6]: Leaving directory '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/boot'
/usr/bin/make -f /«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk -C /«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/efi built_in.o
make[6]: Entering directory '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/efi'
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_GAS_VMX -DHAVE_GAS_EPT -DHAVE_GAS_FSGSBASE -mno-red-zone -mno-sse -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -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 -nostdinc -DHAS_ACPI -DHAS_GDBSX -DHAS_PASSTHROUGH -DHAS_PCI -DHAS_IOPORTS -MMD -MF .boot.o.d -fshort-wchar -DINIT_SECTIONS_ONLY -c boot.c -o boot.o
objdump -h boot.o | sed -n '/[0-9]/{s,00*,0,g;p}' | while read idx name sz rest; do \
	case "$name" in \
	.text|.text.*|.data|.data.*|.bss) \
		test $sz != 0 || continue; \
		echo "Error: size of boot.o:$name is 0x$sz" >&2; \
		exit $(expr $idx + 1);; \
	esac; \
done
Error: size of boot.o:.text is 0x01e9
make[6]: *** [boot.init.o] Error 1
/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk:174: recipe for target 'boot.init.o' failed
make[6]: Leaving directory '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/efi'
make[5]: *** [/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/efi/built_in.o] Error 2
/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk:153: recipe for target '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86/efi/built_in.o' failed
make[5]: Leaving directory '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86'
make[4]: *** [/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/xen] Error 2
Makefile:100: recipe for target '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen/xen' failed
make[4]: Leaving directory '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen'
make[3]: *** [build] Error 2
Makefile:26: recipe for target 'build' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/debian/build/build-hypervisor_amd64_amd64/xen'
make[2]: *** [debian/stamps/build-hypervisor_amd64_amd64] Error 2
debian/rules.real:83: recipe for target 'debian/stamps/build-hypervisor_amd64_amd64' failed
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [build-arch_amd64_none_amd64] Error 2
debian/rules.gen:50: recipe for target 'build-arch_amd64_none_amd64' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:20: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

--- End Message ---
--- Begin Message ---
On Fri, 2015-03-13 at 14:54 +0100, Matthias Klose wrote:
> clone 778181 -1
> reassign -1 src:xen
> thanks
> 
> from the upstream discussion, it doesn't seem to be clear if this is a GCC
> issue. Is this new in GCC 5?

The first I've heard of it was via this bug report and nobody (me
included) seems to be having the issue with gcc 4. I routinely build
with Wheezy's compiler, as does the upstream automated test
infrastructure. I've just given it a go with "gcc (Debian 4.9.1-19)
4.9.1" (from a slightly old Jessie) and it was ok too.

>  your referenced bug number seems a bit old (PR57725).
> 
> in http://lists.xen.org/archives/html/xen-devel/2015-03/msg01692.html
> PR64963 is referenced, but which is marked as fixed upstream.

Closed on 16 February though and the gcc-5 snapshot I was using was
dated 20150204, because my apt update for some reason didn't upgrade
this old chroot properly and I didn't notice.

I've just installed 5-20150307-1 and the issue has gone.

I've closed this Xen bug, but I guess there is a clone floating around
on the gcc-5 now?

> in http://lists.xen.org/archives/html/xen-devel/2015-03/msg01694.html
> you write that you suppose I will take this upstream, without noting me. No I
> will not. Please do the bike shedding with upstream yourself ;)

Sorry, that should have ended "...or he'll ask us to do it" but I was
too lazy to type it.

Ian.

--- End Message ---

Reply to: