Strange characters in the build output window

[edwin]

Hello,

The development environment I have set up is: Widows xp sp3 (English) + CodeBlocks SVN 6205 + Cygwin 1.7.5.

I am porting existing Windows 32bit code using C::B an gcc/g++ to Cygwin for an eventual port to Linux.

Cygwin info:
uname -a returns:
CYGWIN_NT-5.1 PS 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin

I am using gcc-4 and g++-4 on Cygwin. The versions are:
gcc-4 (GCC) 4.3.4 20090804 (release) 1
g++-4 (GCC) 4.3.4 20090804 (release) 1

I see strange characters in C::B's build log and build message's windows. Something like:

.......BuildSettings.h|2345|error: expected ‘,’ or ‘...’ before ‘*’ token|

...can you see the wierd ‘ and other strange character encodings?


It must be a code page issue that I do not have set up properly but I will be darned if I can find the proper settings to make this go away. It is making building somewhat difficult.

Anyway, if this is not changeable somewhere in CodeBlocks, does anyone on this support forum know the setting I can change in Cygwin that will allow gcc/g++ to emit the proper character encoded information to C::B?

I will keep looking in the meantime….

Thank you in advance for your help. CodeBlocks is really excellent and I hope it continues to mature and grow.


edwin

[stahta01]

I suggest trying to set LC_CTYPE to various values and see what works best

Tim S.

One thing to try is en_US.UTF-8 next is just C
Tim S.

[socaldavec]

I know this is an old msg, but it is exactly my issue...  I don't get the answer given or I can't make it work.

I edit c:\cygwin64\home\Dave\.profile

I add after "export LANG=$(locale -uU)"   "LC_CTYPE=en_US.UTF-8" and I get the same kind of odd characters in my compile messages.

Has anyone overcome this problem specifically that can tell me what you have in your .profile (or did  you fix it somewhere else)?

I have extensively searched Google for an answer to no avail.  I also get that this is a gcc and/or g++ issue, but I don't know where else to ask this.

Thank you for your time and patience,

~dave

[Jenna]

Try it with "LC_ALL" and as type you can use "C", that should work for any existing user locales (at least on linux).