qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 2/3] new: debian docker targets for cross-compiling
Date: Tue, 14 Feb 2017 23:18:03 +0800	[thread overview]
Message-ID: <20170214151803.GD20715@lemon.lan> (raw)
In-Reply-To: <87fujgvmf9.fsf@linaro.org>

On Tue, 02/14 15:09, Alex Bennée wrote:
> 
> Peter Maydell <peter.maydell@linaro.org> writes:
> 
> > On 14 February 2017 at 10:07, Alex Bennée <alex.bennee@linaro.org> 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.
> >
> > Is there a particular reason for creating different docker images
> > for each cross target rather than just having one image with
> > all the cross compilers in it?
> 
> Mainly the clashing of build-dependencies. Debian's multi-arch is pretty
> good but you still can't generally have two arches worth of complex
> dependencies installed at once.
> 
> I did originally have one base docker image with all the compilers and
> intended to do the dependencies step as part of test-build. However when
> running as builders the docker images don't actually have network
> ability so couldn't download them.

Yes, having to "prepare", especially to download things, for each test
invocation is not resource friendly for CI too.

Fam

  reply	other threads:[~2017-02-14 15:18 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
2017-02-14 14:30   ` Peter Maydell
2017-02-14 15:09     ` Alex Bennée
2017-02-14 15:18       ` Fam Zheng [this message]
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=20170214151803.GD20715@lemon.lan \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --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).