From: "Alex Bennée" <alex.bennee@linaro.org>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 2/3] new: debian docker targets for cross-compiling
Date: Tue, 14 Feb 2017 15:10:49 +0000 [thread overview]
Message-ID: <87efz0vmdi.fsf@linaro.org> (raw)
In-Reply-To: <20170214142727.GB20715@lemon.lan>
Fam Zheng <famz@redhat.com> writes:
> On Tue, 02/14 22:00, Fam Zheng wrote:
>> On Tue, 02/14 10:07, Alex Bennée wrote:
>> > This provides a basic Debian install with access to the emdebian cross
>> > compilers. The debian-armhf-cross and debian-arm64-cross targets build
>> > on the basic Debian image to allow cross compiling to those targets.
>> >
>> > To build against the cross compiler a cross-compile prefix needs to be
>> > set in the configure options, for example:
>> >
>> > make docker-test-build@debian-arm64-cross \
>> > EXTRA_CONFIGURE_OPTS="--cross-prefix=aarch64-linux-gnu-" \
>> > TARGET_LIST="aarch64-softmmu,aarch64-linux-user"
>>
>> If cross-compile is the only meaningful way to use this image, we probably
>> should bake the configure option into the dockerfile and pick it up
>> automatically in common.rc. What do you think?
>
> The example change is like this:
>
> diff --git a/tests/docker/common.rc b/tests/docker/common.rc
> index 21657e87c6..6865689bb5 100755
> --- a/tests/docker/common.rc
> +++ b/tests/docker/common.rc
> @@ -29,7 +29,7 @@ build_qemu()
> config_opts="--enable-werror \
> ${TARGET_LIST:+--target-list=${TARGET_LIST}} \
> --prefix=$PWD/install \
> - $EXTRA_CONFIGURE_OPTS \
> + $QEMU_CONFIGURE_OPTS $EXTRA_CONFIGURE_OPTS \
> $@"
> echo "Configure options:"
> echo $config_opts
> diff --git a/tests/docker/dockerfiles/debian-arm64-cross.docker b/tests/docker/dockerfiles/debian-arm64-cross.docker
> index 04212629f7..fc1c135e74 100644
> --- a/tests/docker/dockerfiles/debian-arm64-cross.docker
> +++ b/tests/docker/dockerfiles/debian-arm64-cross.docker
> @@ -10,3 +10,4 @@ RUN dpkg --add-architecture arm64
> RUN apt update
> RUN apt install -yy crossbuild-essential-arm64
> RUN apt-get build-dep -yy -a arm64 qemu
> +ENV QEMU_CONFIGURE_OPTS --cross-prefix=aarch64-linux-gnu-
Yeah that seems like a good idea. Then a make
docker-test-build@debian-armhf-cross will work as expected ;-)
--
Alex Bennée
next prev parent reply other threads:[~2017-02-14 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:07 [Qemu-devel] [PATCH v3 0/3] Docker cross-compile targets and user build support Alex Bennée
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 1/3] tests/docker: add basic user mapping support Alex Bennée
2017-02-14 14:22 ` Fam Zheng
2017-02-14 15:11 ` Alex Bennée
2017-02-14 15:20 ` Fam Zheng
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 2/3] new: debian docker targets for cross-compiling Alex Bennée
2017-02-14 14:00 ` Fam Zheng
2017-02-14 14:27 ` Fam Zheng
2017-02-14 15:10 ` Alex Bennée [this message]
2017-02-14 14:30 ` Peter Maydell
2017-02-14 15:09 ` Alex Bennée
2017-02-14 15:18 ` Fam Zheng
2017-02-14 10:07 ` [Qemu-devel] [PATCH v3 3/3] .shippable.yml: new CI provider Alex Bennée
2017-02-14 14:11 ` Fam Zheng
2017-02-14 15:56 ` Alex Bennée
2017-02-15 0:51 ` 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=87efz0vmdi.fsf@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).