Re: Why no strings in error messages?

[Richard Earnshaw <rearnsha at arm dot com>]

On Wed, 2009-08-26 at 09:00 -0400, Bradley Lucier wrote:
> I've never seen the answer to the following question:  Why do some  
> versions of gcc that I build not have string substitutions in error  
> messages?
> 
> I get things like this:
> 
> [lucier@lambda-head lib]$ /pkgs/gcc-mainline/bin/gcc -mcpu=970 -m64 - 
> fschedule-insns -Wno-unused -O1 -fno-math-errno -fschedule-insns2 - 
> fno-trapping-math -fno-strict-aliasing -fwrapv -fomit-frame-pointer - 
> fPIC -fno-common -I"../include" -c _thread-test.i -save-temps
> _thread.c: In function â:
> _thread.c:10035:146: error: â undeclared (first use in this function)
> _thread.c:10035:146: error: (Each undeclared identifier is reported  
> only once
> _thread.c:10035:146: error: for each function it appears in.)

Your locale is set up to generate something your terminal can't display
properly (I've seen this myself).

Either fix your terminal to display the extended char-set properly, or
run your compiler with a simpler locale, eg:

export LANG=c
gcc ...

should do the trick.

If you want to prove to yourself that the variables are there pass the
output through 'od -c'

R.