From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: "qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>,
Eric Blake <eblake@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 00/12] Convert over to use keycodemapdb
Date: Tue, 15 Aug 2017 14:49:45 +0100 [thread overview]
Message-ID: <20170815134945.GM9674@redhat.com> (raw)
In-Reply-To: <85B66A0C-33EF-4DF8-8137-ECCA251A0F2D@gmail.com>
On Tue, Aug 15, 2017 at 09:49:00AM -0400, Programmingkid wrote:
>
> > On Aug 15, 2017, at 4:38 AM, Daniel P. Berrange <berrange@redhat.com> wrote:
> >
> > On Mon, Aug 14, 2017 at 02:46:22PM -0400, Programmingkid wrote:
> >> Sorry but there appears to be an issue with your patchset. I ran this command:
> >>
> >> ./configure --target-list=ppc-softmmu,i386-softmmu
> >>
> >> Then saw this error message:
> >>
> >> error: pathspec 'ui/keycodemapdb' did not match any file(s) known to git.
> >>
> >> Running 'make' I saw this error message:
> >>
> >> make: *** No rule to make target `ui/input-keymap-atset1-to-qcode.c', needed by `Makefile'. Stop.
> >> make: *** Waiting for unfinished jobs....
> >>
> >> Running the 'make clean' command produces this error message:
> >>
> >> make[1]: *** No rule to make target `ui/input-keymap-atset1-to-qcode.c', needed by `Makefile'. Stop.
> >> make: *** [clean] Error 1
> >>
> >> Perhaps a missing patch?
> >
> > No, its a missing "git submodule update --init ui/keycodemapdb" call
>
> Thank you for replying. I tried this command and saw this error message:
>
> error: pathspec 'ui/keycodemapdb' did not match any file(s) known to git.
>
> Note: I'm using version 3. Will test version 4 soon.
>
> I suggest adding the git submodule update info to your cover letter
> saying it is required.
It isn't supposed to be required - its a bug, hence why the tests are
failing.
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-08-15 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 18:46 [Qemu-devel] [PATCH v3 00/12] Convert over to use keycodemapdb Programmingkid
2017-08-15 8:38 ` Daniel P. Berrange
2017-08-15 13:49 ` Programmingkid
2017-08-15 13:49 ` Daniel P. Berrange [this message]
2017-08-15 14:44 ` Programmingkid
[not found] <mailman.1778.1502715001.21954.qemu-devel@nongnu.org>
2017-08-14 13:39 ` Programmingkid
2017-08-14 14:00 ` Daniel P. Berrange
2017-08-14 17:20 ` Programmingkid
2017-08-14 18:20 ` Eric Blake
2017-08-14 18:49 ` Programmingkid
2017-08-14 19:07 ` Eric Blake
2017-08-14 20:30 ` Philippe Mathieu-Daudé
-- strict thread matches above, loose matches on Subject: below --
2017-08-14 12:49 Daniel P. Berrange
2017-08-14 13:05 ` no-reply
2017-08-14 13:06 ` no-reply
2017-08-14 13:06 ` no-reply
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=20170815134945.GM9674@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=programmingkidx@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.