From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] build.sh: Fix perl complaints about locale
Date: Mon, 13 Nov 2017 17:07:58 +0300 [thread overview]
Message-ID: <d4592bf0-a584-80d2-5e11-2c261262b26e@ilbers.de> (raw)
In-Reply-To: <2e4a157d-6981-c979-30f4-56f1fd58790a@ilbers.de>
On 11/13/2017 04:44 PM, Alexander Smirnov wrote:
> Hi,
>
> On 11/13/2017 04:19 PM, Christian Storm wrote:
>>> 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
>
> Hmm, it works as it is for archs different from host machine. I've
> attached 3 build logs for hello application in Stretch: amd64, arm and
> i386 and only *amd64* has locale flood. The others are OK. So that's why
> I think it's rather bug in configscript.
Working on PRoot I've found the following multistrap option:
"ignorenativearch=true"
Probably it could somehow help here...
Alex
>>
>> --- 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
>>
>
next prev parent reply other threads:[~2017-11-13 14:08 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
2017-11-13 13:44 ` Alexander Smirnov
2017-11-13 14:07 ` Alexander Smirnov [this message]
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=d4592bf0-a584-80d2-5e11-2c261262b26e@ilbers.de \
--to=asmirnov@ilbers.de \
--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