From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Rousse Subject: Re: insufficient fix for gcc localised output in stubdom makefile Date: Thu, 15 Jan 2009 12:48:44 +0100 Message-ID: <496F229C.1000800@inria.fr> References: <496E0F93.5050404@inria.fr> <18798.8507.528311.524383@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <18798.8507.528311.524383@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ian Jackson a =E9crit : > Guillaume Rousse writes ("[Xen-devel] insufficient fix for gcc localise= d output in stubdom makefile"): >> There was a slight change in stubdom makefile from 3.3 to 3.3.1, in=20 >> order to use non-localised gcc output: >> GCC_INSTALL =3D $(shell LANG=3DC gcc -print-search-dirs | sed -n -e=20 >> 's/install: \(.*\)/\1/p') >=20 > This is a joke, right ? The purpose of gcc -print-search-dirs > is to provide information to other programs. Its output should not be > localised. >=20 > If it is, then that is a bug in your compiler. As a workaround, set > whatever environment variables are necessary to make it not be so > stupid. Well, that's not really new apparently: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D14351 My point here is not to discuss if this is a bug or not, rather than the=20 workaround used in xen makefile is not enough for everyone out there.