Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752651AbdFNNLM (ORCPT ); Wed, 14 Jun 2017 09:11:12 -0400 Received: from smtprelay.synopsys.com ([198.182.60.111]:59508 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752124AbdFNNLL (ORCPT ); Wed, 14 Jun 2017 09:11:11 -0400 From: Alexey Brodkin To: "mmarek@suse.com" CC: "linux-kernel@vger.kernel.org" , "linux-kbuild@vger.kernel.org" , "yamada.masahiro@socionext.com" , "linux-snps-arc@lists.infradead.org" , "Vineet.Gupta1@synopsys.com" Subject: Re: [PATCH] Unexport LANG env variable Thread-Topic: [PATCH] Unexport LANG env variable Thread-Index: AQHS5QuAbUq5hzGQbEiUqJMpujuR5aIkMV4AgAACYYA= Date: Wed, 14 Jun 2017 13:11:07 +0000 Message-ID: <1497445867.6424.36.camel@synopsys.com> References: <1497444056-24962-1-git-send-email-abrodkin@synopsys.com> <51f658dc-215a-6c0c-0ab9-d1164812a56d@suse.com> In-Reply-To: <51f658dc-215a-6c0c-0ab9-d1164812a56d@suse.com> Accept-Language: en-US, ru-RU Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.121.8.122] Content-Type: text/plain; charset="utf-8" Content-ID: <4FCC27F6141A854399871360E92DD51D@internal.synopsys.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v5EDBGjv004543 Content-Length: 1490 Lines: 35 Hi Michal, On Wed, 2017-06-14 at 15:02 +0200, Michal Marek wrote: > Dne 14.6.2017 v 14:40 Alexey Brodkin napsal(a): > > > > In those cases when we parse output of standard utilities like readelf > > etc we rely on a particular sentences. For example for ARC we extract > > an entry-point from vmlinux like that: > > ---------------------->8-------------------- > > readelf -h vmlinux | grep "Entry point address" | grep -o 0x.* > > ---------------------->8-------------------- > > > > And in case LANG is set to anything other than en_XX we're getting > > nothing and subsequent execution of mkimage utility fails. > > > > Probably there're more cases like that but given people rarely > > use non-English locales on their dev machines problems like the one > > above are not very visible. > > I'm all for this change but the *.po files in the gcc tree must have > been created for a reason: > >   https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_gcc-2Dmirror_gcc_tree_master_gcc_po&d=DwICBA&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes > 0GFDDl656eViXO7breS55ytWkhpk5R81I&m=v2ilYYv6Z0WzVaIys3sCQdK3QBI9gqH7hUmoTGPpJ44&s=S3B79SHovtt1-wLRtngTUM0dKWMiokGE75HIrfgkbbc&e=  That's for sure. But then how may we have a predictable environment for our machinery? I do realize that with that change in place people will start seeing non-translated messages from other tools like compiler etc. But probably that's not the worst idea as well because it helps googling :) -Alexey