From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15461] QtVirtualKeyboard segfaults
Date: Wed, 22 Mar 2023 16:36:37 +0000 [thread overview]
Message-ID: <bug-15461-163-TvLkkz5zrc@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 #6 from Peter Seiderer <ps.report@gmx.net> ---
With (at least) gcc-12.2.0 on RPi4 (32-bit) changing from
BR2_OPTIMIZE_S=y
to
BR2_OPTIMIZE_2=y
seems sufficient...
Or maybe it is worth a try to bump the versions (as the last on is from
2022-05-17, see [1])...
[1]
https://git.buildroot.net/buildroot/commit/package/qt5?id=558d62490b4486f47248c63aa0eceaaa27e3069c
--
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-03-22 16:36 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 [this message]
2023-06-21 13:08 ` bugzilla
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-TvLkkz5zrc@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 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).