On 01/08/2017 11:36 AM, Tom H wrote: > On Sun, Jan 8, 2017 at 11:14 AM, Helmut Jarausch <jarau...@skynet.be> wrote: >> >> The strange C.UTF-8 , which was suggested by one of the devolopers of >> media-gfx/darktable, did cause the problems. The error messages were >> strange and misleading. >> >> Urs wrote >> >>> You can generate a "fake" C.UTF-8 locale with localedef: >>> # localedef -i en_US -f UTF-8 C.UTF-8 >>> and remove it when no longer needed: >>> # localedef --delete-from-archive C.utf8 >>> Don't blame me for ugly side effects... >> >> Many thanks for this unusual hint. With this I can build the >> GIT-version of darktable. >> >> Is the strange locale name C.UTF-8 a "specialty" of darktable or have >> other distributions such a locale? > > C.UTF-8 is (and has been for a while) a valid Debian locale,installed > by default with libc. And it became, somewhat recently, a valid Fedora > locale (so as not to have to install any additional locales in a > container, over and above the default libc ones, C, C.UTF-8, and > POSIX). > >
It is possible to create this on Gentoo (with some warnings) by creating a symlink /usr/share/i18n/locales/C that points to "POSIX", then adding "C.UTF-8" to locale.gen as normal. -- Jonathan Callen
signature.asc
Description: OpenPGP digital signature
