Your message dated Tue, 9 Mar 2021 13:40:48 +0300
with message-id <182ad3fd-1133-1abd-50c4-003cefb34...@msgid.tls.msk.ru>
and subject line Re: Bug#972789: qemu: FTBFS on arm{el,hf}:
/<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not
compatible
has caused the Debian Bug report #972789,
regarding qemu: FTBFS on arm{el,hf}:
/<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not
compatible
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 ow...@bugs.debian.org
immediately.)
--
972789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:5.1+dfsg-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
binNMUs of qemu for the libbrlapi transition failed to build on armel
and armhf:
| cc -iquote /<<PKGBUILDDIR>>/b/qemu/linux-user/m68k -iquote linux-user/m68k
-iquote /<<PKGBUILDDIR>>/tcg/arm -isystem /<<PKGBUILDDIR>>/linux-headers
-isystem /<<PKGBUILDDIR>>/b/qemu/linux-headers -iquote . -iquote
/<<PKGBUILDDIR>> -iquote /<<PKGBUILDDIR>>/accel/tcg -iquote
/<<PKGBUILDDIR>>/include -iquote /<<PKGBUILDDIR>>/disas/libvixl
-I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -pthread
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -fPIE
-DPIE -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings
-Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv -std=gnu99 -g
-O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wold-style-declaration
-Wold-style-definition -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self
-Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels
-Wexpansion-to-defined -Wno-missing-include-dirs -Wno-shift-negative-value
-Wno-psabi -fstack-protector-strong -I/usr/include/p11-kit-1
-DSTRUCT_IOVEC_DEFINED -I/usr/include/libpng16 -I/usr/include/spice-server
-I/usr/include/spice-1 -I/usr/include/capstone -isystem ../linux-headers
-iquote .. -iquote /<<PKGBUILDDIR>>/target/m68k -DNEED_CPU_H -iquote
/<<PKGBUILDDIR>>/include -I/<<PKGBUILDDIR>>/linux-user/m68k
-I/<<PKGBUILDDIR>>/linux-user/host/arm -I/<<PKGBUILDDIR>>/linux-user
-Ilinux-user/m68k -MMD -MP -MT linux-user/m68k/signal.o -MF
linux-user/m68k/signal.d -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g -c -o
linux-user/m68k/signal.o /<<PKGBUILDDIR>>/linux-user/m68k/signal.c
| /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is
not compatible
| 44 | };
| | ^
| <array_type 0xb5b48ba0
| type <integer_type 0xb6f94420 unsigned int asm_written public unsigned SI
| size <integer_cst 0xb692ee58 constant 32>
| unit-size <integer_cst 0xb692ee70 constant 4>
| align:32 warn_if_not_align:0 symtab:-1229976864 alias-set -1
canonical-type 0xb6f94420 precision:32 min <integer_cst 0xb693f0f0 0> max
<integer_cst 0xb693f0d8 4294967295>
| pointer_to_this <pointer_type 0xb6944ba0>>
| SI size <integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70 4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb5b48ba0
| domain <integer_type 0xb676d6c0
| type <integer_type 0xb6f94060 sizetype public unsigned SI size
<integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70 4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb6f94060 precision:32 min <integer_cst 0xb692ee88 0> max <integer_cst
0xb692e000 4294967295>>
| SI size <integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70
4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb676d6c0 precision:32 min <integer_cst 0xb692ee88 0> max <integer_cst
0xb692ee88 0>>>
| /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_MODE’ of
‘TYPE_CANONICAL’ is not compatible
| <array_type 0xb5b48ba0
| type <integer_type 0xb6f94420 unsigned int asm_written public unsigned SI
| size <integer_cst 0xb692ee58 constant 32>
| unit-size <integer_cst 0xb692ee70 constant 4>
| align:32 warn_if_not_align:0 symtab:-1229976864 alias-set -1
canonical-type 0xb6f94420 precision:32 min <integer_cst 0xb693f0f0 0> max
<integer_cst 0xb693f0d8 4294967295>
| pointer_to_this <pointer_type 0xb6944ba0>>
| SI size <integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70 4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb5b48ba0
| domain <integer_type 0xb676d6c0
| type <integer_type 0xb6f94060 sizetype public unsigned SI size
<integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70 4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb6f94060 precision:32 min <integer_cst 0xb692ee88 0> max <integer_cst
0xb692e000 4294967295>>
| SI size <integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70
4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb676d6c0 precision:32 min <integer_cst 0xb692ee88 0> max <integer_cst
0xb692ee88 0>>>
| <array_type 0xb5b48b40
| type <integer_type 0xb6054f00 abi_ulong asm_written public unsigned SI
| size <integer_cst 0xb692ee58 constant 32>
| unit-size <integer_cst 0xb692ee70 constant 4>
| user align:16 warn_if_not_align:0 symtab:-1241131856 alias-set -1
canonical-type 0xb6f94420 precision:32 min <integer_cst 0xb693f0f0 0> max
<integer_cst 0xb693f0d8 4294967295>
| pointer_to_this <pointer_type 0xb5aaef60>>
| no-force-blk BLK size <integer_cst 0xb692ee58 32> unit-size <integer_cst
0xb692ee70 4>
| user align:16 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb5b48ba0
| domain <integer_type 0xb676d6c0
| type <integer_type 0xb6f94060 sizetype public unsigned SI size
<integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70 4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb6f94060 precision:32 min <integer_cst 0xb692ee88 0> max <integer_cst
0xb692e000 4294967295>>
| SI size <integer_cst 0xb692ee58 32> unit-size <integer_cst 0xb692ee70
4>
| align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0xb676d6c0 precision:32 min <integer_cst 0xb692ee88 0> max <integer_cst
0xb692ee88 0>>>
| /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: internal compiler error:
‘verify_type’ failed
See
https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=armhf&ver=1%3A5.1%2Bdfsg-4%2Bb1&stamp=1603242447&raw=0
for example
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Fri, 23 Oct 2020 18:50:42 +0200 Sebastian Ramacher <sramac...@debian.org>
wrote:
Source: qemu
Version: 1:5.1+dfsg-4
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
Since some version of gcc-10 this issue stopped appearing.
Closing this bugreport now.
If you think this is incorrect, fell free to reopen it.
Thanks,
/mjt
--- End Message ---
