From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] package/xterm: fix compilation with uClibc
Date: Sun, 3 Sep 2023 09:51:43 +0200 [thread overview]
Message-ID: <ZPQ7D+xaRQDl1n8L@waldemar-brodkorb.de> (raw)
Compile errors out with:
./util.c: In function 'decode_wcwidth':
./util.c:5506:26: error: 'wcwidth' undeclared (first use in this function); did you mean 'mk_wcwidth'?
5506 | my_wcwidth = wcwidth;
| ^~~~~~~
| mk_wcwidth
./util.c:5506:26: note: each undeclared identifier is reported only once for each function it appears in
uClibc only exposes wcwidth when __USE_XOPEN is defined.
Fixes:
- http://autobuild.buildroot.net/results/1c0/1c03a8016d480d9c3fc3112849b1a125df243cab
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/xterm/0001-uClibc-wcwidth.patch | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 package/xterm/0001-uClibc-wcwidth.patch
diff --git a/package/xterm/0001-uClibc-wcwidth.patch b/package/xterm/0001-uClibc-wcwidth.patch
new file mode 100644
index 0000000000..ee0416ec78
--- /dev/null
+++ b/package/xterm/0001-uClibc-wcwidth.patch
@@ -0,0 +1,13 @@
+Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
+Upstream: N/A patch sent via email
+diff -Nur xterm-376.orig/util.c xterm-376/util.c
+--- xterm-376.orig/util.c 2022-09-25 19:46:22.000000000 +0200
++++ xterm-376/util.c 2023-09-03 09:05:36.227133537 +0200
+@@ -69,6 +69,7 @@
+
+ #if OPT_WIDE_CHARS
+ #if defined(HAVE_WCHAR_H) && defined(HAVE_WCWIDTH)
++#define __USE_XOPEN
+ #include <wchar.h>
+ #endif
+ #include <wcwidth.h>
--
2.39.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-09-03 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 7:51 Waldemar Brodkorb [this message]
2023-09-11 20:55 ` [Buildroot] [PATCH] package/xterm: fix compilation with uClibc Thomas Petazzoni via buildroot
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=ZPQ7D+xaRQDl1n8L@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.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