From: "Alex Bennée" <alex.bennee@linaro.org>
To: famz@redhat.com
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH v1 0/2] s390x cross Docker target
Date: Mon, 27 Feb 2017 14:30:26 +0000 [thread overview]
Message-ID: <20170227143028.16428-1-alex.bennee@linaro.org> (raw)
Hi,
A build failure on s390 was reported so to investigate I put together
a cross-compile environment to debug it. As it turned out the report
was a false positive but the cross target might still be useful for
people who don't have big iron handy ;-)
Alex Bennée (2):
new: dockerfiles/debian-s390-cross
.shippable: add s390x-cross target
.shippable.yml | 2 ++
tests/docker/dockerfiles/debian-s390x-cross.docker | 22 ++++++++++++++++++++++
2 files changed, 24 insertions(+)
create mode 100644 tests/docker/dockerfiles/debian-s390x-cross.docker
--
2.11.0
next reply other threads:[~2017-02-27 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 14:30 Alex Bennée [this message]
2017-02-27 14:30 ` [Qemu-devel] [PATCH v1 1/2] new: dockerfiles/debian-s390-cross Alex Bennée
2017-02-28 22:11 ` Philippe Mathieu-Daudé
2017-02-27 14:30 ` [Qemu-devel] [PATCH v1 2/2] .shippable: add s390x-cross target Alex Bennée
2017-02-28 11:57 ` [Qemu-devel] [PATCH v1 0/2] s390x cross Docker target Fam Zheng
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=20170227143028.16428-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=famz@redhat.com \
--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).