From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/10] Ui 20171011 patches
Date: Fri, 13 Oct 2017 10:15:58 +0200 [thread overview]
Message-ID: <1507882558.21465.4.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA9uXw7XYOBu9cKY+B=OWNbS=cRp7BKcXacLTaRLx9RWdA@mail.gmail.com>
On Wed, 2017-10-11 at 15:37 +0100, Peter Maydell wrote:
> On 11 October 2017 at 09:35, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > The following changes since commit
> > 567d0a19c7998fa366598b83d5a6e5f0759d3ea9:
> >
> > Merge remote-tracking branch 'remotes/ehabkost/tags/x86-and-
> > machine-pull-request' into staging (2017-10-10 13:25:46 +0100)
> >
> > are available in the git repository at:
> >
> > git://git.kraxel.org/qemu tags/ui-20171011-pull-request
> >
> > for you to fetch changes up to
> > 92328b7104ffc825f10c33f3fd1866e940a523f7:
> >
> > ui/gtk: Fix deprecation of vte_terminal_copy_clipboard (2017-10-
> > 11 10:03:31 +0200)
> >
> > ----------------------------------------------------------------
> > ui: use keycodemapdb for key code mappings, part one (v2)
> > ui: add qemu-keymap, update reverse keymaps (for qemu -k $map)
> > ui: fix for vte 0.50
> >
> > ----------------------------------------------------------------
>
> Build failures:
>
> NetBSD:
> CC ui/input-keymap.o
> /root/qemu/ui/input-keymap.c:8:44: fatal error:
> ui/input-keymap-linux-to-qcode.c: No such file or directory
> #include "ui/input-keymap-linux-to-qcode.c"
> ^
>
> FreeBSD:
>
>
> CC ui/input-keymap.o
> /root/qemu/ui/input-keymap.c:8:10: fatal error:
> 'ui/input-keymap-linux-to-qcode.c' file not found
> #include "ui/input-keymap-linux-to-qcode.c"
> ^
>
> OpenBSD:
>
> gmake: Entering directory '/home/qemu/build/all'
> /bin/sh: ./scripts/git-submodule.sh: No such file or directory
> gmake: Leaving directory '/home/qemu/build/all'
> gmake: Entering directory '/home/qemu/build/all'
> GIT
> /bin/sh: ./scripts/git-submodule.sh: No such file or directory
> gmake: *** [Makefile:30: git-submodule-update] Error 1
> gmake: Leaving directory '/home/qemu/build/all'
> gmake: *** Waiting for unfinished jobs....
> gmake: Entering directory '/home/qemu/build/all'
> config-host.mak is out-of-date, running configure
> Install prefix /usr/local
> [configure output snipped]
> gmake: Leaving directory '/home/qemu/build/all'
>
> AArch32 Linux:
>
> make: Entering directory '/home/peter.maydell/qemu/build/all-a32'
> config-host.mak is out-of-date, running configure
> Install prefix /usr/local
> BIOS directory /usr/local/share/qemu
> [...]
> VxHS block device no
> GEN config-host.h
> GEN module_block.h
> GEN ui/input-keymap-linux-to-qcode.c
> GEN ui/input-keymap-qcode-to-qnum.c
> GEN ui/input-keymap-qnum-to-qcode.c
> GIT ui/keycodemapdb dtc
> GEN trace/generated-tcg-tracers.h
> GEN trace/generated-helpers-wrappers.h
> GEN trace/generated-helpers.h
> GEN trace/generated-helpers.c
> Makefile:30: recipe for target 'git-submodule-update' failed
> make: *** [git-submodule-update] Error 128
> make: *** Waiting for unfinished jobs....
> make: Leaving directory '/home/peter.maydell/qemu/build/all-a32'
>
>
> The OpenBSD failure is because make now tries to run a
> script that uses #!/bin/bash, and this machine doesn't
> have bash installed. Do we really need to add bash to
> our build-dependencies? The script doesn't seem like it's
> doing anything that critically requires bash...
>
> thanks
> -- PMM
New pull out, with bash dropped, repo switched to qemu mirror and one
additional gtk fix picked up from the list.
cheers,
Gerd
prev parent reply other threads:[~2017-10-13 8:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:35 [Qemu-devel] [PULL 00/10] Ui 20171011 patches Gerd Hoffmann
2017-10-11 8:35 ` [Qemu-devel] [PULL 01/10] build: automatically handle GIT submodule checkout for dtc Gerd Hoffmann
2017-10-11 8:35 ` [Qemu-devel] [PULL 02/10] docker: don't rely on submodules existing in the main checkout Gerd Hoffmann
2017-10-11 8:35 ` [Qemu-devel] [PULL 03/10] ui: add keycodemapdb repository as a GIT submodule Gerd Hoffmann
2017-10-11 8:35 ` [Qemu-devel] [PULL 04/10] ui: convert common input code to keycodemapdb Gerd Hoffmann
2017-10-11 8:35 ` [Qemu-devel] [PULL 05/10] ui: convert key events to QKeyCodes immediately Gerd Hoffmann
2017-10-11 8:36 ` [Qemu-devel] [PULL 06/10] ui: don't export qemu_input_event_new_key Gerd Hoffmann
2017-10-11 8:36 ` [Qemu-devel] [PULL 07/10] tools: add qemu-keymap Gerd Hoffmann
2017-10-11 8:36 ` [Qemu-devel] [PULL 08/10] Add pc-bios/keymaps/Makefile Gerd Hoffmann
2017-10-11 8:36 ` [Qemu-devel] [PULL 10/10] ui/gtk: Fix deprecation of vte_terminal_copy_clipboard Gerd Hoffmann
2017-10-11 14:37 ` [Qemu-devel] [PULL 00/10] Ui 20171011 patches Peter Maydell
2017-10-11 14:49 ` Kamil Rytarowski
2017-10-11 15:49 ` Daniel P. Berrange
2017-10-11 16:45 ` Peter Maydell
2017-10-12 8:24 ` Daniel P. Berrange
2017-10-12 9:00 ` Peter Maydell
2017-10-12 9:30 ` Gerd Hoffmann
2017-10-12 9:33 ` Daniel P. Berrange
2017-10-12 10:04 ` Gerd Hoffmann
2017-10-12 10:07 ` Daniel P. Berrange
2017-10-12 10:11 ` Peter Maydell
2017-10-12 10:13 ` Gerd Hoffmann
2017-10-12 10:14 ` Daniel P. Berrange
2017-10-12 9:51 ` Peter Maydell
2017-10-12 10:01 ` Gerd Hoffmann
2017-10-13 8:15 ` Gerd Hoffmann [this message]
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=1507882558.21465.4.camel@redhat.com \
--to=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).