Bug#972789: qemu: FTBFS on arm{el,hf}: /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible
- To: 972789@bugs.debian.org
- Subject: Bug#972789: qemu: FTBFS on arm{el,hf}: /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible
- From: Michael Tokarev <mjt@tls.msk.ru>
- Date: Thu, 10 Dec 2020 00:59:57 +0300
- Message-id: <[🔎] 9b43c8d1-63d3-6a1c-e04a-fd755a2a3863@msgid.tls.msk.ru>
- Reply-to: Michael Tokarev <mjt@tls.msk.ru>, 972789@bugs.debian.org
- In-reply-to: <20201028113041.GA2613488@ramacher.at>
- References: <20201023165042.GA782632@ramacher.at> <1c70ccb5-1be2-9279-e55c-dcd58300a1f6@msgid.tls.msk.ru> <20201028113041.GA2613488@ramacher.at> <20201028113041.GA2613488@ramacher.at> <20201023165042.GA782632@ramacher.at>
On Wed, 28 Oct 2020 12:30:41 +0100 Sebastian Ramacher <sramacher@debian.org> wrote:
On 2020-10-24 07:38:39 +0300, Michael Tokarev wrote:
...
> Hmm. So this looks like a gcc ICE bug. Here's the code in question:
> ...
> > | /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: internal compiler error: ‘verify_type’ failed
>
> I'm not sure what I have to do with this, besides reassigning it to gcc.
>
> BTW, symbol TYPE_CANONICAL is not used/referenced by qemu sources.
Indeed, that's a bug in gcc which was already reported upstream.
Reassigning accordingly.
I dunno what happened, either it was new gcc or new qemu, but this issue
is gone - as of today's upload of qemu 5.2 it built successfully on both
armhf and armel.
Guess we can close this bugreport, what do you think?
/mjt
Reply to: