Try using g++ --version command at cmd Because for me also g++ -version or g++ -v command hasn't worked.

Very simple.

Go to Command Prompt and type

gcc -v

if gcc is installed on your PC, it should display a host of information, starting with the sentence

Using built-in specs

and that will indicate that gcc is installed on your computer.

1. Type gcc at the Terminal prompt. If it says "command not found", you don't. Otherwise, you do.
2. If that fails, then install from your OSX CD.

Run gcc --version, the result will be something like this:

gcc (GCC) 4.4.0
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

If this doesn't work you might not have the compiler setup in your PATH correctly (I believe this is common if using MinGW on Windows), in which case you can first check where the compiler is located by doing the following within Code::Blocks:

• Menubar Settings -> Compiler and Debugger
• Select GNU GCC Compiler
• Select the Toolchain executables tab

Then, using a command line, move to the directory given, then in to the bin subdirectory, then try running gcc --version from there.

In order to get that information you should type the commands: gcc -v or gcc --version. For more details see the man pages for gcc http://linux.die.net/man/1/gcc

The symlink to the 4.8.2 directory is nothing to worry about, it's normal for the libstdc++ headers on Red Hat Enterprise Linux (and therefore CentOS) to be arranged like that.

gcc --version will tell you the version of the gcc executable in your path.

rpm -q libstdc++-devel will tell you the version of the package that owns the C++ standard library headers.

rpm -ql libstdc++-devel will list the files installed by that package, which will include the files under /usr/include/c++/4.8.2

rpm --verify libstdc++-devel will check that you haven't messed up the C++ headers by replacing them with something else.

The error is more concerning, that implies you have messed something up. My guess would be it's in the from [...omitted by myself as it is irrelevant] part, which may actually be very relevant. std::locale should be declared in <bits/locale_classes.h> which is included before <bits/locale_facets_nonio.h>, so if it wasn't declared my guess is that you have some header that defines _LOCALE_CLASSES_H and prevents the standard library header from being read. Do not define include guards that start with underscores, they are reserved names.