From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/6] Ui 20171005 patches
Date: Thu, 5 Oct 2017 16:55:04 +0100 [thread overview]
Message-ID: <20171005155504.GK12106@redhat.com> (raw)
In-Reply-To: <CAFEAcA-9F++KngXrHGE=t7qZhdU2gCGKKSwHXYdLR6EhEfO4Qg@mail.gmail.com>
On Thu, Oct 05, 2017 at 04:12:12PM +0100, Peter Maydell wrote:
> On 5 October 2017 at 11:01, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > The following changes since commit d147f7e815f97cb477e223586bcb80c316ae10ea:
> >
> > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-10-03 16:27:24 +0100)
> >
> > are available in the git repository at:
> >
> > git://git.kraxel.org/qemu tags/ui-20171005-pull-request
> >
> > for you to fetch changes up to 47247520ac44592cc7343138380bd6099f83262f:
> >
> > ui: don't export qemu_input_event_new_key (2017-10-05 11:21:51 +0200)
> >
> > ----------------------------------------------------------------
> > ui: use keycodemapdb for key code mappings, part one
> >
> > ----------------------------------------------------------------
>
> Fails to build, all platforms:
>
> make: Entering directory `/home/pm215/qemu/build/all'
> config-host.mak is out-of-date, running configure
> make: *** No rule to make target `ui/input-keymap-linux-to-qcode.c',
> needed by `Makefile'. Stop.
> make: *** Waiting for unfinished jobs....
> Install prefix /usr/local
> BIOS directory /usr/local/share/qemu
> firmware path /usr/local/share/qemu-firmware
> binary directory /usr/local/bin
> library directory /usr/local/lib
> module directory /usr/local/lib/qemu
> [etc]
> replication support yes
> VxHS block device no
> make: Leaving directory `/home/pm215/qemu/build/all'
>
> That make complains about the missing .c file before it has
> finished running configure looks suspicious. I think there's
> a race here with parallel make.
Am I right in thinking from this snippet, that you applied the patch
series to an existing checkout with built files and then just did a
'make', as opposed todoing a git clean + configure + make sequence.
That would explain why this failed - the list of submodules is not
populated in the pre-existing config-host.mak. So we wouldn't checkout
the new submodules, and so the deps in the GENERATED_FILES list won't
be satisfied. I'll figure out how to make this correctly cope with
gracefully upgrading from a dev's existing checkout...
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 :|
next prev parent reply other threads:[~2017-10-05 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 10:01 [Qemu-devel] [PULL 0/6] Ui 20171005 patches Gerd Hoffmann
2017-10-05 10:01 ` [Qemu-devel] [PULL 1/6] build: automatically handle GIT submodule checkout for dtc Gerd Hoffmann
2017-10-05 10:01 ` [Qemu-devel] [PULL 2/6] docker: don't rely on submodules existing in the main checkout Gerd Hoffmann
2017-10-05 10:01 ` [Qemu-devel] [PULL 3/6] ui: add keycodemapdb repository as a GIT submodule Gerd Hoffmann
2017-10-05 10:01 ` [Qemu-devel] [PULL 4/6] ui: convert common input code to keycodemapdb Gerd Hoffmann
2017-10-05 10:01 ` [Qemu-devel] [PULL 5/6] ui: convert key events to QKeyCodes immediately Gerd Hoffmann
2017-10-05 10:01 ` [Qemu-devel] [PULL 6/6] ui: don't export qemu_input_event_new_key Gerd Hoffmann
2017-10-05 10:10 ` [Qemu-devel] [PULL 0/6] Ui 20171005 patches no-reply
2017-10-05 15:12 ` Peter Maydell
2017-10-05 15:55 ` Daniel P. Berrange [this message]
2017-10-05 16:05 ` Peter Maydell
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=20171005155504.GK12106@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@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).