All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: C.UTF-8 may not be present resulting in failed build
Date: Wed, 4 Nov 2015 11:14:16 +0300	[thread overview]
Message-ID: <5639BE58.5070007@gmail.com> (raw)
In-Reply-To: <CAEaD8JNesYkMd6u2XcrWarLN4BjFu7bftL9y0RfscNiw19GwiQ@mail.gmail.com>

03.11.2015 21:44, Vladimir 'phcoder' Serbinenko пишет:
> Le 2 nov. 2015 7:48 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> 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 use them in tests as an easy alternative to real translations. But we
> can generate them without this locale. We could replace y sed command with
> bunch of s and use pain C locale

But it has C.UTF-8 not only for sed, but for all other commands 
invocations. Is it really needed


      reply	other threads:[~2015-11-04  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 18:47 C.UTF-8 may not be present resulting in failed build Andrei Borzenkov
2015-11-02 22:04 ` Mike Gilbert
2015-11-03 18:44 ` Vladimir 'phcoder' Serbinenko
2015-11-04  8:14   ` Andrei Borzenkov [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=5639BE58.5070007@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    /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.