Re: C.UTF-8 may not be present resulting in failed build

2015-11-04 Thread Andrei Borzenkov
03.11.2015 21:44, Vladimir 'phcoder' Serbinenko пишет: Le 2 nov. 2015 7:48 PM, "Andrei Borzenkov" a écrit : Extra catalogs added in da0d5b3f explicitly require C.UTF-8 locale. This locale may not be present (e.g. openSUSE does not have it). Upstream gettext (and hence en@quot rules) does no

Re: C.UTF-8 may not be present resulting in failed build

2015-11-03 Thread Vladimir 'phcoder' Serbinenko
Le 2 nov. 2015 7:48 PM, "Andrei Borzenkov" a écrit : > > Extra catalogs added in da0d5b3f explicitly require C.UTF-8 locale. This locale may not be present (e.g. openSUSE does not have it). > > Upstream gettext (and hence en@quot rules) does not use it. Is forcing this locale really needed? > > We

Re: C.UTF-8 may not be present resulting in failed build

2015-11-02 Thread Mike Gilbert
On Mon, Nov 2, 2015 at 1:47 PM, Andrei Borzenkov wrote: > Extra catalogs added in da0d5b3f explicitly require C.UTF-8 locale. This > locale may not be present (e.g. openSUSE does not have it). I think it is specific to Debian-derived distros actually. We don't have it on Gentoo either. _

C.UTF-8 may not be present resulting in failed build

2015-11-02 Thread Andrei Borzenkov
Extra catalogs added in da0d5b3f explicitly require C.UTF-8 locale. This locale may not be present (e.g. openSUSE does not have it). Upstream gettext (and hence en@quot rules) does not use it. Is forcing this locale really needed? ___ Grub-devel mai