From: Zhang Wen <zhw2101024@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-trivial@nongnu.org, pbonzini@redhat.com,
marcandre.lureau@redhat.com, berrange@redhat.com,
thuth@redhat.com, philmd@linaro.org, qemu-devel@nongnu.org
Subject: Re: building qemu on a system with libxkbcommon installed but not xkeyboard-config produces an core dump
Date: Thu, 8 Feb 2024 10:00:26 +0800 [thread overview]
Message-ID: <CAKjfnjoMe2C5YzuUPPD7PPERhXoYgrmsDVPjR+rizjYHMUcpBQ@mail.gmail.com> (raw)
In-Reply-To: <CAKjfnjpCz=hrpZXj7uS=OQdpvkKPEFa24s3QYS4TqNZALcykJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 121 bytes --]
Here's my error message and core file attached.
--
Key fingerprint:
419F 72F3 F3A9 36EE 1B72 B00B C1C3 4BD4 FDA3 362F
[-- Attachment #2: err.log --]
[-- Type: application/octet-stream, Size: 264 bytes --]
Generating pc-bios/keymaps/ar with a custom command
FAILED: pc-bios/keymaps/ar
/sources/qemu/qemu-8.2.0/build/qemu-keymap -f pc-bios/keymaps/ar -l ara
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
ninja: build stopped: subcommand failed.
[-- Attachment #3: core.qemu-keymap --]
[-- Type: application/octet-stream, Size: 9048064 bytes --]
next prev parent reply other threads:[~2024-02-08 2:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 8:13 building qemu on a system with libxkbcommon installed but not xkeyboard-config produces an core dump Zhang Wen
2024-02-01 12:11 ` Michael Tokarev
2024-02-01 12:49 ` Michael Tokarev
2024-02-01 12:57 ` Peter Maydell
2024-02-01 12:59 ` Michael Tokarev
2024-02-06 6:35 ` Zhang Wen
2024-02-06 7:08 ` Michael Tokarev
2024-02-06 7:50 ` Zhang Wen
2024-02-08 2:00 ` Zhang Wen [this message]
2024-02-08 11:52 ` 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=CAKjfnjoMe2C5YzuUPPD7PPERhXoYgrmsDVPjR+rizjYHMUcpBQ@mail.gmail.com \
--to=zhw2101024@gmail.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
/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).