From: Michael Tokarev <mjt@tls.msk.ru>
To: Zhang Wen <zhw2101024@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: 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: Tue, 6 Feb 2024 10:08:39 +0300 [thread overview]
Message-ID: <e292f18b-18cb-4b67-9db4-df938aa19d3d@tls.msk.ru> (raw)
In-Reply-To: <CAKjfnjrCu1R6LE46AYf0+SGXs6994APhRvgSNWR8wfp=mnp3Fw@mail.gmail.com>
06.02.2024 09:35, Zhang Wen:
...
> I'm so sorry for the misspelling in my initial post and the confusion
> caused by that.
That's no problem, things happen.
> I'm building my own system following the Linux From Scratch package, which is at
> https://www.linuxfromscratch.org.
> I accidently built libxkbcommon package but not xkeyboard-config
> package, and then
> while building qemu I saw this problem. it's a little difficult to
> find the root cause from
> this error message, so I sent this patch to seek for help from upstream.
Okay, so it is mostly a self-built/self-installed linux. That works too.
So how the problem manifests itself? What the actual error message is?
You mentioned some segfault iirc, care to share some details?
It's not a problem at all to pick this change up, but I'd love to know
more details about this first :)
Thanks,
/mjt
next prev parent reply other threads:[~2024-02-06 7:09 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 [this message]
2024-02-06 7:50 ` Zhang Wen
2024-02-08 2:00 ` Zhang Wen
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=e292f18b-18cb-4b67-9db4-df938aa19d3d@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--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 \
--cc=zhw2101024@gmail.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).