From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14931] package/qt5/qt5webengine: build fails with unicode/uchar.h not found
Date: Tue, 23 Aug 2022 15:13:59 +0000 [thread overview]
Message-ID: <bug-14931-163-lrODusoanj@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14931-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14931
--- Comment #1 from Stefan Mayrhofer <stefan.mayrhofer@ginzinger.com> ---
(In reply to wg from comment #0)
Hi Wolfgang,
we are currently working on a solution and already have found one (it needs
some more polishing but until it gets upstreamed, you can take a look at it):
https://paste.debian.net/1251470/
--
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:[~2022-08-23 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 16:40 [Buildroot] [Bug 14931] New: package/qt5/qt5webengine: build fails with unicode/uchar.h not found bugzilla
2022-08-23 15:13 ` bugzilla [this message]
2022-08-24 9:49 ` [Buildroot] [Bug 14931] " bugzilla
2023-05-09 13:50 ` bugzilla
2023-09-11 18:41 ` bugzilla
2023-10-25 21:46 ` bugzilla
2024-06-15 15:03 ` 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-14931-163-lrODusoanj@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