From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13551] 2021.02.rc2: Unicode not work on qt 5.15.2
Date: Tue, 23 Feb 2021 06:24:42 +0000 [thread overview]
Message-ID: <bug-13551-163-CquIUCp5A3@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13551-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13551
--- Comment #2 from Alfredo Pons Menargues <alfredo.pons@gmail.com> ---
You test is very good to reproduce the probem in a simple way.
In my Ubuntu 20.04 I get the same result as you. It's correct.
But in the buildroot image for rpi3 (2021.02.rc2) I get:
$ ./test 2>&1 | hexdump -C
00000000 3f 0a |?.|
00000002
I don't understand why this is happening.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-23 6:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 7:37 [Buildroot] [Bug 13551] New: 2021.02.rc2: Unicode not work on qt 5.15.2 bugzilla at busybox.net
2021-02-22 19:06 ` [Buildroot] [Bug 13551] " bugzilla at busybox.net
2021-02-23 6:24 ` bugzilla at busybox.net [this message]
2021-02-23 6:25 ` bugzilla at busybox.net
2021-02-23 19:29 ` bugzilla at busybox.net
2021-02-28 16:12 ` bugzilla at busybox.net
2021-03-17 16:01 ` bugzilla at busybox.net
2021-03-17 16:02 ` bugzilla at busybox.net
2021-03-17 18:54 ` bugzilla at busybox.net
2021-03-17 18:56 ` bugzilla at busybox.net
2021-03-17 18:57 ` bugzilla at busybox.net
2021-03-17 23:00 ` bugzilla at busybox.net
2021-03-18 7:35 ` bugzilla at busybox.net
2021-03-18 19:28 ` bugzilla at busybox.net
2021-05-07 13:07 ` bugzilla at busybox.net
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-13551-163-CquIUCp5A3@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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