The GNU Standard C++ Library v3 is an ongoing project to implement the ISO 14882 Standard C++ library as described in chapters 17 through 27 and annex D. For those who want to see exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source is available over anonymous SVN, and can even be browsed over the web.

Hopefully, not much. The goal of libstdc++ is to produce a fully-compliant, fully-portable Standard Library. After that, we're mostly done: there won't be any more compliance work to do. However: The ISO Committee will meet periodically to review Defect Reports in the C++ Standard. Undoubtedly some of these will result in changes to the Standard, which will be reflected in patches to libstdc++. Some of that is already happening, see 4.3.

Complete instructions are not given here (this is a FAQ, not an installation document), but the tools required are few: A 3.x or later release of GCC. Either install a suitable package for your system, or compile GCC from the sources. Note that building GCC is much easier and more automated than building the GCC 2.[78] series was. If you are using GCC 2.

Nathan Myers gave the best of all possible answers, responding to a Usenet article asking this question: Sooner, if you help.

The compiler in use reports a thread model other than 'single'. This can be tested via output from gcc -v. Multi-thread capable versions of gcc output something like this: %gcc -v Using built-in specs. ... Thread model: posix gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) Requisite command-line flags are used for atomic operations and threading. Examples of this include -pthread and -march=native, although specifics vary depending on the host environment. See Machine Dependent Options.

Because GCC advances so rapidly, development and testing of libstdc++ is being done almost entirely under that compiler. If you are curious about whether other, lesser compilers (*grin*) support libstdc++, you are more than welcome to try. Configuring and building the library (see above) will still require certain tools, however. Also keep in mind that building libstdc++ does not imply that your compiler will be able to use all of the features found in the C++ Standard Library.

Depending on your platform and library version, the message might be similar to one of the following: ./a.out: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory /usr/libexec/ld-elf.so.1: Shared object "libstdc++.so.6" not found This doesn't mean that the shared library isn't installed, only that the dynamic linker can't find it.

The wide-character parts of the GCC Standard C++ Library (libstdc++) have not yet been fully ported to Windows. Alternatives and discussion on this can be found here.

FC3 comes with gcc-3.4 which includes libstdc++.so.6 and it is the default gcc. You will need to install the "compat-libstdc++" package as mppd depends on libstdc++.so.5. Back To Top