Guile 2.2.4 warnings

Guile 2.2.4 warnings

[Tommi Höynälänmaa]

Hello

I just installed Guile 2.2.4 to a chroot sid (Debian) environment. Guile 
gives the following warnings on startup:

---cut here---

guile: warning: failed to install locale
warning: failed to install locale: Invalid argument

---cut here---

Are these something important?

      - Tommi Höynälänmaa

Re: Guile 2.2.4 warnings

[Alex Vong]

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Hello Tommi,

Tommi Höynälänmaa <tommi.hoynalanmaa@gmail.com> writes:

> Hello
>
> I just installed Guile 2.2.4 to a chroot sid (Debian)
> environment. Guile gives the following warnings on startup:
>
> ---cut here---
>
> guile: warning: failed to install locale
> warning: failed to install locale: Invalid argument
>
> ---cut here---
>
> Are these something important?
>
In my experience, these warnings are noncritical. In the past, guix
worked fine even with these warngings (they are gone now). I think you
would be fine if the guile program you run uses only ascii in I/O
(otherwise some garbage characters might get printed).

However, I think we should find out the root cause of these warnings. My
guess is that this is because guile cannot find locales from glibc. I
might investigate using a debian sid chroot later if I have time.

>      - Tommi Höynälänmaa

Cheers,
Alex

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

Re: Guile 2.2.4 warnings

[Mark H Weaver]

Hi,

Tommi Höynälänmaa <tommi.hoynalanmaa@gmail.com> writes:

> I just installed Guile 2.2.4 to a chroot sid (Debian)
> environment. Guile gives the following warnings on startup:
>
> ---cut here---
>
> guile: warning: failed to install locale
> warning: failed to install locale: Invalid argument
>
> ---cut here---

This indicates that setlocale(3) failed to set the locale specified by
your environment variable settings (LANG, LC_ALL, LC_CTYPE, etc),
probably because the associated locale data is not installed in the
chroot.

> Are these something important?

This is an area where my knowledge is relatively weak, but I guess the
implications of failing to set the locale include:

* ASCII encoding will likely be used by default by Guile, e.g. for file
  and terminal I/O, interpretation of command-line arguments and
  environment variables, and interpretation of file names on disk.
  Normally, your locale encoding (probably UTF-8) would be used by
  default for these purposes.

* Certain operations such as locale-aware string comparisons, formatting
  of dates, numbers, monetary amounts, etc, would normally be affected
  by your locale setting.  If the locale cannot be set, I guess it will
  use the default behaviors, primarily based on US English.

If only ASCII characters are used, and if you don't mind the US English
locale conventions being used, it probably doesn't matter.

      Mark