qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: thuth@redhat.com,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, wainersm@redhat.com, willianr@redhat.com,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/2] tests/docker: promote debian-riscv64-cross to a full image
Date: Wed, 15 Sep 2021 16:03:38 +0100	[thread overview]
Message-ID: <YUILSp1ssORl9zir@redhat.com> (raw)
In-Reply-To: <145f1b51-bffc-85c2-f4d6-3240ba51611a@amsat.org>

On Wed, Sep 15, 2021 at 05:01:23PM +0200, Philippe Mathieu-Daudé wrote:
> On 9/15/21 10:15 AM, Alex Bennée wrote:
> > Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> >> On 9/14/21 8:58 PM, Richard Henderson wrote:
> >>> From: Alex Bennée <alex.bennee@linaro.org>
> >>>
> >>> To be able to cross build QEMU itself we need to include a few more
> >>> libraries. These are only available in Debian's unstable ports repo
> >>> for now so we need to base the riscv64 image on sid with the the
> >>> minimal libs needed to build QEMU (glib/pixman).
> >>>
> >>> The result works but is not as clean as using build-dep to bring in
> >>> more dependencies. However sid is by definition a shifting pile of
> >>> sand and by keeping the list of libs minimal we reduce the chance of
> >>> having an image we can't build. It's good enough for a basic cross
> >>> build testing of TCG.
> >>>
> > <snip>
> >>> diff --git a/tests/docker/dockerfiles/debian-riscv64-cross.docker b/tests/docker/dockerfiles/debian-riscv64-cross.docker
> >>> index 2bbff19772..594d97982c 100644
> >>> --- a/tests/docker/dockerfiles/debian-riscv64-cross.docker
> >>> +++ b/tests/docker/dockerfiles/debian-riscv64-cross.docker
> >>> @@ -1,12 +1,48 @@
> >>>  #
> >>> -# Docker cross-compiler target
> >>> +# Docker cross-compiler target for riscv64
> >>>  #
> >>> -# This docker target builds on the debian Buster base image.
> >>> +# Currently the only distro that gets close to cross compiling riscv64
> >>> +# images is Debian Sid (with unofficial ports). As this is a moving
> >>> +# target we keep the library list minimal and are aiming to migrate
> >>> +# from this hack as soon as we are able.
> >>>  #
> >>> -FROM qemu/debian10
> >>> +FROM docker.io/library/debian:sid-slim
> >>> +
> >>> +# Add ports
> >>> +RUN apt update && \
> >>> +    DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
> >>> +    DEBIAN_FRONTEND=noninteractive eatmydata apt update -yy && \
> >>> +    DEBIAN_FRONTEND=noninteractive eatmydata apt upgrade -yy
> >>> +
> >>> +# Install common build utilities
> >>> +RUN DEBIAN_FRONTEND=noninteractive eatmydata apt install -yy \
> >>> +    bc \
> >>> +    build-essential \
> >>> +    ca-certificates \
> >>> +    debian-ports-archive-keyring \
> >>> +    dpkg-dev \
> >>> +    gettext \
> >>> +    git \
> >>> +    ninja-build \
> >>> +    pkg-config \
> >>> +    python3
> >>
> >> Alex, why not using a debian-sid intermediate image?
> > 
> > Well we removed the original debian-sid image a while ago having excised
> > images that used it. Basing things on sid does cause problems given it's
> > such a moving feast. Rather than encouraging others to build sid based
> > images we decided it made more sense to make this a pure standalone
> > image which we can migrate away from at the first opportunity.
> 
> Yeah, which is why I'm worried we'll get the same problem...
> 
> So this image can't be used as gating IMO.

Yeah, IME from babysitting libvirt CI, 'sid' containers break in dep
solving more often than is acceptable for a mandatory job, especially
for non-x86 arches.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-09-15 15:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 18:58 [PATCH 0/2] gitlab-ci: Add riscv64 cross builds Richard Henderson
2021-09-14 18:58 ` [PATCH 1/2] tests/docker: promote debian-riscv64-cross to a full image Richard Henderson
2021-09-15  7:35   ` Philippe Mathieu-Daudé
2021-09-15  8:15     ` Alex Bennée
2021-09-15 15:01       ` Philippe Mathieu-Daudé
2021-09-15 15:03         ` Daniel P. Berrangé [this message]
2021-09-14 18:58 ` [PATCH 2/2] gitlab: Add cross-riscv64-system, cross-riscv64-user Richard Henderson
2021-09-15  7:36   ` Philippe Mathieu-Daudé
2021-09-15 14:31   ` Willian Rampazzo
2021-09-15 15:03   ` Philippe Mathieu-Daudé
2021-09-15 16:32     ` Richard Henderson
2021-09-17 18:18       ` Philippe Mathieu-Daudé
2021-09-15  6:15 ` [PATCH 0/2] gitlab-ci: Add riscv64 cross builds Alex Bennée

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=YUILSp1ssORl9zir@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=willianr@redhat.com \
    /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).