From: Fam Zheng <famz@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, stefanha@redhat.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
jsnow@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [RFC PATCH 3/4] tests: Add mingw 32/64 cross compiling
Date: Thu, 4 Feb 2016 10:29:44 +0800 [thread overview]
Message-ID: <20160204022944.GF5187@ad.usersys.redhat.com> (raw)
In-Reply-To: <56B217E4.2070603@weilnetz.de>
On Wed, 02/03 16:08, Stefan Weil wrote:
> Am 03.02.2016 um 15:36 schrieb Fam Zheng:
> > Only fedora22 has the required toolchain so it's not run elsewhere.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > tests/docker/mingw.sh | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> > create mode 100755 tests/docker/mingw.sh
> >
> > diff --git a/tests/docker/mingw.sh b/tests/docker/mingw.sh
> > new file mode 100755
> > index 0000000..0f103cd
> > --- /dev/null
> > +++ b/tests/docker/mingw.sh
> > @@ -0,0 +1,14 @@
> > +#!/bin/bash
> > +
> > +if [ "$IMAGE_TAG" != "fedora22" ]; then
> > + echo "Mingw test skipped"
> > + exit 0
> > +fi
> > +
> > +cd $(mktemp -d)
> > +for prefix in x86_64-w64-mingw32- i686-w64-mingw32-; do
> > + $QEMU_SRC/configuire --cross-prefix=$prefix \
>
> configure?
Yes, how could I not notice the type? @.@
>
> > + --target-list=x86_64-softmmu,aarch64-softmmu
> > + make $MAKEFLAGS
> > +done
> > +
>
> I suggest to add a trace backend as well (my tests run with
> --enable-trace-backend=stderr, so maybe you want to choose
> a different one).
Will do.
>
> Another useful option for configure is --enable-debug.
> The compilation will be much faster and detect nearly
> the same kind of problems as the standard compilation
> (use of uninitialized variables won't be detected).
OK.
Thanks for taking a look!
Fam
>
> Regards,
> Stefan
>
next prev parent reply other threads:[~2016-02-04 2:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 14:36 [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 1/4] tests: Introduce Docker based tests Fam Zheng
2016-02-04 11:58 ` Daniel P. Berrange
2016-02-05 6:17 ` Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 2/4] tests: Add clang docker test Fam Zheng
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 3/4] tests: Add mingw 32/64 cross compiling Fam Zheng
2016-02-03 15:08 ` Stefan Weil
2016-02-04 2:29 ` Fam Zheng [this message]
2016-02-04 11:24 ` Paolo Bonzini
2016-02-03 16:14 ` Eric Blake
2016-02-04 2:28 ` Fam Zheng
2016-02-04 12:00 ` Daniel P. Berrange
2016-02-03 14:36 ` [Qemu-devel] [RFC PATCH 4/4] tests: Add travis container test case Fam Zheng
2016-02-03 15:24 ` [Qemu-devel] [RFC PATCH 0/4] tests: Introducing docker tests Stefan Hajnoczi
2016-02-04 2:43 ` Fam Zheng
2016-02-04 11:26 ` Paolo Bonzini
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=20160204022944.GF5187@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).