From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@buildbot.b1-systems.de, gollub@b1-systems.de, kvm@vger.kernel.org
Subject: Re: buildbot failure in kvm on s390
Date: Tue, 19 Nov 2013 12:46:04 +0100 [thread overview]
Message-ID: <20131119124604.31cfba16@gondolin> (raw)
In-Reply-To: <20131117114508.GU2008@redhat.com>
On Sun, 17 Nov 2013 13:45:08 +0200
Gleb Natapov <gleb@redhat.com> wrote:
> On Sun, Nov 17, 2013 at 05:31:32AM +0100, kvm@buildbot.b1-systems.de wrote:
> > The Buildbot has detected a new failure on builder s390 while building kvm.
> > Full details are available at:
> > http://buildbot.b1-systems.de/kvm/builders/s390/builds/1063
> >
> > Buildbot URL: http://buildbot.b1-systems.de/kvm/
> >
> > Buildslave for this Build: b1_kvm_1
> >
> > Build Reason: The Nightly scheduler named 'nightly_master' triggered this build
> > Build Source Stamp: [branch master] HEAD
> > Blamelist:
> >
> > BUILD FAILED: failed compile
> >
> cc1: error: unrecognized command line option "-march=z196"
>
> Does not looks like something KVM related.
Looks like this is caused by a2c0844965534e2276e5b0c0dc8a0952658412a4,
which updated the s390 defconfig to optimize for z196. IIRC, support
for z196 was added with gcc 4.6, so either the buildbot's gcc needs to
be updated, or the config modified to build for an older revision.
next prev parent reply other threads:[~2013-11-19 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 4:31 buildbot failure in kvm on s390 kvm
2013-11-17 11:45 ` Gleb Natapov
2013-11-19 11:46 ` Cornelia Huck [this message]
2013-11-19 11:57 ` Christian Berendt
2013-11-19 14:13 ` Cornelia Huck
-- strict thread matches above, loose matches on Subject: below --
2013-03-05 4:08 kvm
2013-02-26 4:40 kvm
2012-03-13 4:20 kvm
2011-12-26 4:16 kvm
2011-09-08 3:03 kvm
2011-07-13 3:16 kvm
2011-06-20 3:18 kvm
2011-05-07 3:06 kvm
2010-12-05 2:07 kvm
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=20131119124604.31cfba16@gondolin \
--to=cornelia.huck@de.ibm.com \
--cc=gleb@redhat.com \
--cc=gollub@b1-systems.de \
--cc=kvm@buildbot.b1-systems.de \
--cc=kvm@vger.kernel.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).