From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Unicode problem with check-uniq-files
Date: Thu, 22 Mar 2018 21:25:32 +0100 [thread overview]
Message-ID: <20180322202532.GA4580@scaer> (raw)
In-Reply-To: <5ffd29df-7b21-122a-2d50-03fc86f29224@jcz.nl>
Jaap, All,
On 2018-03-22 11:43 +0100, Jaap Crezee spake thusly:
> On 03/21/18 22:44, Yann E. MORIN wrote:
> > If you change your LC_ALL et al to an UTF-8 locale, it will work again,
> > I believe.
>
> That is not working for me:
>
> /bin/sh: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
"UTF-8" by itself is not a valid locale definition. A valid locale is
made of three firelds:
ll_CC[.encoding]
with:
ll: the ISO 639-1 2-letter language name, e.g. fr, en, cs...
CC: the ISO 3166-1 alpha-2 2letter country code, e.g. FR, CA, UK, US,
CS...
encoding: a relatively-free-form field that defines the character set
encoding. In practice, only UTF-8 is ever used AFAICS...
E.g.:
fr_FR.UTF-8 french, in France, UTF-8 charset
fr_CA.UTF-8 french, in Canada (Quebec), UTF-8 charset
en_GB.UTF-8 english, Great Britain, UTF-8 charset
Locale can define a large set of representations:
- number: decimal separator, currency symbol position, negative
symbol and its position...
- address: separator between number and streetname, ZIP code...
- collation, i.e. ordering rules, like uppercase vs. lowercase...
and a sh!tload other stuff, see: man 7 locale
> >>> Finalizing target directory
> # Check files that are touched by more than one package
> /bin/sh: warning: setlocale: LC_ALL: cannot change locale (UTF-8)
See what locales are available on your system:
locale -a
Then use one of those, e.g.:
LC_ALL=en_US.UTF-8 ./support/scripts/check-uniq-files -t target \
/data/work/jcz/git/jidiot/clients/innr/buildroot_development/output/build/packages-file-list.txt
> BTW my LANG is set to "C".
That's OK. ;-) I had been using POSIX for years before I decided to
enter the 3rd millenai, and switched to a mix of en_GB.UTF-8 and
fr_FR.UTF-8 a few years ago...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-03-22 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 20:45 [Buildroot] Unicode problem with check-uniq-files Jaap Crezee
2018-03-19 21:32 ` Yann E. MORIN
2018-03-20 7:48 ` Jaap Crezee
2018-03-21 21:44 ` Yann E. MORIN
2018-03-22 10:43 ` Jaap Crezee
2018-03-22 20:25 ` Yann E. MORIN [this message]
[not found] ` <f965a6fb-db48-b39c-6f49-46a025fc63ad@jcz.nl>
2018-03-22 20:41 ` Yann E. MORIN
2018-03-22 20:46 ` Yann E. MORIN
2018-03-22 21:12 ` Jaap Crezee
2018-03-23 21:23 ` Arnout Vandecappelle
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=20180322202532.GA4580@scaer \
--to=yann.morin.1998@free.fr \
--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