From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: "qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v5 08/12] char: convert the escc device to keycodemapdb
Date: Mon, 18 Sep 2017 10:28:11 +0100 [thread overview]
Message-ID: <20170918092811.GB2951@redhat.com> (raw)
In-Reply-To: <E7665638-9EE7-45B0-AF95-BC37863AC0DA@gmail.com>
On Fri, Sep 15, 2017 at 02:32:14PM -0400, Programmingkid wrote:
> Sorry but I saw this error when I tried your patches:
>
> OBJC ui/cocoa.o
> CC ui/curses.o
> ui/input-keymap.c:17:10: fatal error: 'ui/input-keymap-qcode-to-sun.c' file not
> found
> #include "ui/input-keymap-qcode-to-sun.c"
> ^
> 1 error generated.
> make: *** [ui/input-keymap.o] Error 1
> make: *** Waiting for unfinished jobs....
>
>
> I could not find this file.
Yes, its a bug in this series - just build without the sparc system
emulators to avoid it.
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-09-18 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 18:32 [Qemu-devel] [PATCH v5 08/12] char: convert the escc device to keycodemapdb Programmingkid
2017-09-18 9:28 ` Daniel P. Berrange [this message]
2017-09-18 14:49 ` Programmingkid
-- strict thread matches above, loose matches on Subject: below --
2017-09-12 12:37 [Qemu-devel] [PATCH v5 00/12] Convert over to use keycodemapdb Daniel P. Berrange
2017-09-12 12:37 ` [Qemu-devel] [PATCH v5 08/12] char: convert the escc device to keycodemapdb 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=20170918092811.GB2951@redhat.com \
--to=berrange@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 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).