All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: Yegor Yefremov <yegorslists@googlemail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/mg: needs a toolchain with wchar support
Date: Tue, 20 Oct 2026 16:38:40 +0200	[thread overview]
Message-ID: <f1d8180348d4dd29527aeacf0767c48a936b28c5.camel@gmail.com> (raw)
In-Reply-To: <20261020135300.3973040-1-yegorslists@googlemail.com>


[-- Attachment #1.1: Type: text/plain, Size: 752 bytes --]

On Tue, 2026-10-20 at 15:53 +0200, Yegor Yefremov wrote:
> Since version 4.2, mg uses iswalnum() from <wctype.h> to tell whether
> a UTF-8 character is part of a word (upstream commit ee22ef729b16
> "Tell UTF-8 words by their Unicode class"). This breaks the build with
> toolchains that lack wide character support, such as uClibc without
> WCHAR:
> 
> utf8.c:23:10: fatal error: wctype.h: No such file or directory
>    23 | #include <wctype.h>
>       |          ^~~~~~~~~~
> 
> Add a dependency on BR2_USE_WCHAR, together with the matching comment.

Thank you Yegor, my bad!

I'll upstream a configure check for wctype.h so we can drop this
restriction in Buildroot in a future update.

Best regards
 /Joachim


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-10-20 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 13:53 [Buildroot] [PATCH] package/mg: needs a toolchain with wchar support Yegor Yefremov
2026-10-20 14:04 ` Thomas Petazzoni via buildroot
2026-10-20 14:38 ` Joachim Wiberg [this message]

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=f1d8180348d4dd29527aeacf0767c48a936b28c5.camel@gmail.com \
    --to=troglobit@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=yegorslists@googlemail.com \
    /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.