From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Andrew Jones <drjones@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] git master build failure
Date: Fri, 17 Jun 2016 21:45:12 +0200 [thread overview]
Message-ID: <66646eb9-b86a-bcf3-ed9a-b20107814a93@redhat.com> (raw)
In-Reply-To: <CAFEAcA-gM68DzwHePDYkiqfXeD8LX2Z3NGyJG8-sMM+mKZbbQA@mail.gmail.com>
On 06/17/16 14:55, Peter Maydell wrote:
> On 17 June 2016 at 13:41, Mark Cave-Ayland
> <mark.cave-ayland@ilande.co.uk> wrote:
>> Thank you looking into this. I know that some workarounds have been
>> applied for similar bugs in Peter's setup, but in general should I
>> assume that out-of-the-box Debian oldstable is now no longer supported
>> to build QEMU?
(I have no stake in this, just took an interest in it for some reason.)
> I would kind of prefer us to work around the compiler issue if
> it's not too difficult to do so. Otherwise, just configure
> with --disable-werror.
I agree working it around is preferable, if we can find a deterministic
way to do that. I'm afraid it will require someone to look into, and
understand, the internal AST representation of gcc (with -fdump-tree-*),
and then perturb it through the QEMU source sufficiently.
Also, how about filing that backport bug for Debian? If they backport
the gcc fix, then the issue is solved -- people can be expected to
update their Debian systems fully, before they do any heavy-lifting with
them (like building QEMU).
Thanks
Laszlo
prev parent reply other threads:[~2016-06-17 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 7:14 [Qemu-devel] git master build failure Mark Cave-Ayland
2016-06-15 9:48 ` Andrew Jones
2016-06-15 10:08 ` Mark Cave-Ayland
2016-06-15 10:23 ` Andrew Jones
2016-06-15 11:26 ` Mark Cave-Ayland
2016-06-15 11:46 ` Mark Cave-Ayland
2016-06-15 12:35 ` Laszlo Ersek
2016-06-17 12:41 ` Mark Cave-Ayland
2016-06-17 12:55 ` Peter Maydell
2016-06-17 19:45 ` Laszlo Ersek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66646eb9-b86a-bcf3-ed9a-b20107814a93@redhat.com \
--to=lersek@redhat.com \
--cc=drjones@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).