qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v6 2/6] docker: don't rely on submodules existing in the main checkout
Date: Fri, 29 Sep 2017 10:35:27 +0800	[thread overview]
Message-ID: <20170929023450.GE26066@lemon.lan> (raw)
In-Reply-To: <20170928095216.GF12919@redhat.com>

On Thu, 09/28 10:52, Daniel P. Berrange wrote:
> On Thu, Sep 28, 2017 at 05:44:53PM +0800, Fam Zheng wrote:
> > On Thu, 09/28 09:44, Daniel P. Berrange wrote:
> > > When building the tarball to pass into the docker/vm test image,
> > > the code relies on the git submodules being checked out in the
> > > main checkout.
> > > 
> > > ie if the developer has not run 'git submodule update --init dtc'
> > > most (all?) of the docker tests will fail due to the missing dtc
> > > package in the test images.
> > 
> > Not all, fail only in envs/configs where libfdt devel doesn't exist.
> 
> I didn't test all of them but of the ~5 I did test all failed, so I
> just assumed none contain libftd-devel, since you have patchew
> manually check it out.

Patchew does it just because mingw needs it, this is not required for native
build:

$ git grep libfdt tests/docker
tests/docker/dockerfiles/centos6.docker:    libfdt-devel \
tests/docker/dockerfiles/centos7.docker:    libfdt-devel \
tests/docker/dockerfiles/fedora.docker:    glib2-devel pixman-devel zlib-devel SDL-devel libfdt-devel \
tests/docker/dockerfiles/min-glib.docker:RUN yum install -y libfdt-devel ccache
tests/docker/dockerfiles/ubuntu.docker:    libspice-protocol-dev libnss3-dev libfdt-dev \

Fam

  reply	other threads:[~2017-09-29  2:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28  8:44 [Qemu-devel] [PATCH v6 0/6] Initial support for keycodemapdb GIT submodule Daniel P. Berrange
2017-09-28  8:44 ` [Qemu-devel] [PATCH v6 1/6] build: automatically handle GIT submodule checkout for dtc Daniel P. Berrange
2017-09-28  8:44 ` [Qemu-devel] [PATCH v6 2/6] docker: don't rely on submodules existing in the main checkout Daniel P. Berrange
2017-09-28  9:44   ` Fam Zheng
2017-09-28  9:52     ` Daniel P. Berrange
2017-09-29  2:35       ` Fam Zheng [this message]
2017-09-28 22:59     ` Alistair Francis
2017-09-28  8:44 ` [Qemu-devel] [PATCH v6 3/6] ui: add keycodemapdb repository as a GIT submodule Daniel P. Berrange
2017-09-28  8:44 ` [Qemu-devel] [PATCH v6 4/6] ui: convert common input code to keycodemapdb Daniel P. Berrange
2017-09-28  8:44 ` [Qemu-devel] [PATCH v6 5/6] ui: convert key events to QKeyCodes immediately Daniel P. Berrange
2017-09-28  8:44 ` [Qemu-devel] [PATCH v6 6/6] ui: don't export qemu_input_event_new_key Daniel P. Berrange
2017-09-28  8:53 ` [Qemu-devel] [PATCH v6 0/6] Initial support for keycodemapdb GIT submodule no-reply
2017-09-28  9:27   ` Daniel P. Berrange

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=20170929023450.GE26066@lemon.lan \
    --to=famz@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).