From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15461] QtVirtualKeyboard segfaults
Date: Wed, 21 Jun 2023 13:08:17 +0000 [thread overview]
Message-ID: <bug-15461-163-XzFMGQ4Gxg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15461-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15461
--- Comment #7 from stijn.vermeir+bugzilla@dioss.com ---
(In reply to Peter Seiderer from comment #6)
I tried a build today with Qt versions bumped like this:
qtbase 29400a683f96867133b28299c0d0bd6bcf40df35
qtdeclarative 540c4e4a5def8c350a49bb68380b787ae62490c6
qtsvg 7e6a3b38b2e898d90cef68a146cd36fda22e4363
qtvirtualkeyboard 72373522141dd3206183eb5fa56ae1c36a6d4c2b
I got these commit ids from here:
https://invent.kde.org/qt/qt/qt5/-/commit/da2e0a59fa38644a95047fe389d955dc71b31fc8
I was using buildroot 2023.02.2 internal toolchain for this with gcc-12.3.0.
The virtual keyboard still segfaults.
I am also trying with gcc-10 now to see if this fixes the segfault here.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-21 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 2:43 [Buildroot] [Bug 15461] New: QtVirtualKeyboard segfaults bugzilla
2023-03-21 13:23 ` [Buildroot] [Bug 15461] " bugzilla
2023-03-21 13:42 ` bugzilla
2023-03-22 0:53 ` bugzilla
2023-03-22 2:08 ` bugzilla
2023-03-22 13:51 ` bugzilla
2023-03-22 16:36 ` bugzilla
2023-06-21 13:08 ` bugzilla [this message]
2023-06-21 14:46 ` bugzilla
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=bug-15461-163-XzFMGQ4Gxg@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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.