From: Christian Storm <christian.storm@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] build.sh: Fix perl complaints about locale
Date: Mon, 13 Nov 2017 14:19:31 +0100 [thread overview]
Message-ID: <20171113131931.tnbt64umjgcmmne7@MD1KR9XC.ww002.siemens.net> (raw)
In-Reply-To: <6c84c20e-96df-03d5-7f60-0c31597d9813@ilbers.de>
> On 11/13/2017 03:21 PM, Christian Storm wrote:
> > The log.do_build is flooded by perl's locale complaints:
> >
> > perl: warning: Setting locale failed.
> > perl: warning: Please check that your locale settings:
> > LANGUAGE = (unset),
> > LC_ALL = "en_US.UTF-8",
> > LANG = (unset)
> > are supported and installed on your system.
> > perl: warning: Falling back to the standard locale ("C").
> >
> > Make perl happy by explicitly giving it the C locale.
> >
> > Signed-off-by: Christian Storm <christian.storm@siemens.com>
> > ---
> > meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-devtools/buildchroot/files/build.sh b/meta/recipes-devtools/buildchroot/files/build.sh
> > index 19d554e..e53d359 100644
> > --- a/meta/recipes-devtools/buildchroot/files/build.sh
> > +++ b/meta/recipes-devtools/buildchroot/files/build.sh
> > @@ -23,4 +23,4 @@ for i in configure aclocal.m4 Makefile.am Makefile.in; do
> > done
> >
> > # Build the package
> > -dpkg-buildpackage
> > +LC_ALL=C LANGUAGE=C LANG=C dpkg-buildpackage
> >
>
> There is code that should setup locales for current buildchroot:
>
> https://github.com/ilbers/isar/blob/master/meta/recipes-devtools/buildchroot/files/configscript.sh#L8
>
> So it would be nice to fix this globally instead of local solution.
Sure, but this alone doesn't solve the problem as you have to put the
locale into every (sudo) environment. Then, what about
--- a/meta/recipes-devtools/buildchroot/files/build.sh
+++ b/meta/recipes-devtools/buildchroot/files/build.sh
@@ -3,6 +3,8 @@
# This software is a part of ISAR.
# Copyright (C) 2015-2017 ilbers GmbH
+[ -r /etc/default/locale ] && . /etc/default/locale
+
# Go to build directory
cd $1
--
for which I could send a patch if this is OK for you..
> BTW, which target distro do you use, Stretch? I already have this
> issue in todo list, but you are welcome to fix this. :-)
Yes, stretch.
Besten Gru�,
Christian
--
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany
next prev parent reply other threads:[~2017-11-13 13:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 12:21 Christian Storm
2017-11-13 12:49 ` Alexander Smirnov
2017-11-13 13:19 ` Christian Storm [this message]
2017-11-13 13:44 ` Alexander Smirnov
2017-11-13 14:07 ` Alexander Smirnov
2017-11-13 14:16 ` Christian Storm
2017-11-13 14:35 ` Alexander Smirnov
2017-11-13 15:24 ` Christian Storm
2017-11-13 16:10 ` Henning Schild
2017-11-13 16:50 ` Alexander Smirnov
2017-11-13 17:06 ` Henning Schild
2017-11-13 17:19 ` Alexander Smirnov
2017-11-14 8:41 ` Christian Storm
2017-11-16 13:17 ` Alexander Smirnov
2017-11-17 10:12 ` Christian Storm
2017-11-17 10:42 ` Alexander Smirnov
2017-11-21 8:42 ` Henning Schild
2017-11-21 8:56 ` Alexander Smirnov
2017-11-21 18:04 ` Henning Schild
2017-11-21 18:12 ` Alexander Smirnov
2017-11-21 18:32 ` Henning Schild
2017-11-21 18:40 ` Alexander Smirnov
2017-11-26 22:09 ` Alexander Smirnov
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=20171113131931.tnbt64umjgcmmne7@MD1KR9XC.ww002.siemens.net \
--to=christian.storm@siemens.com \
--cc=isar-users@googlegroups.com \
/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