Re: messed up error messages from gcc

2009-12-02 Thread Mike Castle
On Wed, Dec 2, 2009 at 12:44 PM, Sven Joachim wrote: > Maybe your terminal is not in Unicode mode? Good possibility, but, I thought that would only matter when non-ascii characters came into play. Oh... ok.. I just found the UTF 8 item on xterm and there actually is a minor difference: $ LANG

Re: messed up error messages from gcc

2009-12-02 Thread Sven Joachim
On 2009-12-02 21:35 +0100, Mike Castle wrote: > I guess this boils down to: is this a bug in gcc or a bug in my set up? Probably there is something wrong on your system, because gcc works as expected in your example here: , | % LANG=en_US.UTF-8 gcc -Wall -Werror t.c | cc1: warnings being tr

Re: messed up error messages from gcc

2009-12-02 Thread Mike Castle
On Wed, Dec 2, 2009 at 11:14 AM, Mike Castle wrote: > So, what's the proper solution to this?  Do I need to install > something?  Or rebuild a locale database somewhere? (if the latter, I > would have thought that it would have been done automatically upon > appropriate installs along the way.)  J

Re: messed up error messages from gcc

2009-12-02 Thread Mike Castle
On Wed, Dec 2, 2009 at 10:41 AM, Kumar Appaiah wrote: > Could you please try running LC_ALL=C gcc -Wall -Werror t.c and let us > know if that solves the issue? Yup. That did it. Thanks for the quick analysis. LANG= gcc ... had the same effect. That's what I get for letting it set the darned

Re: messed up error messages from gcc

2009-12-02 Thread Kumar Appaiah
On Wed, Dec 02, 2009 at 10:36:20AM -0800, Mike Castle wrote: > I typically keep my environment pretty stripped down, and so it may > turn out that I'm missing some package that causes the following > problem. But I've not yet been able to figure it out. I'm hoping the > masses out here will immed