#[1]home
-
+
libstdc++ Frequently Asked Questions
-
+
The latest version of this document is always available at
[2]http://sources.redhat.com/libstdc++/faq/.
-
+
To the [3]libstdc++-v3 homepage.
_________________________________________________________________
-
+
Questions
-
+
1. [4]General Information
1. [5]What is libstdc++-v3?
2. [6]Why should I use libstdc++?
6. [33]Is libstdc++-v3 thread-safe?
7. [34]How do I get a copy of the ISO C++ Standard?
_________________________________________________________________
-
+
1.0 General Information
-
+
1.1 What is libstdc++-v3?
The GNU Standard C++ Library v3, or libstdc++-2.90.x, is an ongoing
how far the project has come, or just want the latest bleeding-edge
code, the up-to-date source is available over anonymous CVS, and can
even be browsed over the Web (see below).
-
+
A more formal description of the V3 goals can be found in the official
[36]design document.
_________________________________________________________________
-
+
1.2 Why should I use libstdc++?
The completion of the ISO C++ standardization gave the C++ community a
Library. However, all existing C++ implementations are (as the Draft
Standard used to say) "incomplet and incorrekt," and many suffer from
limitations of the compilers that use them.
-
+
The GNU C/C++/FORTRAN/<pick-a-language> compiler (gcc, g++, etc) is
widely considered to be one of the leading compilers in the world. Its
development has recently been taken over by the [37]GCC team. All of
the rapid development and near-legendary [38]portability that are the
hallmarks of an open-source project are being applied to libstdc++.
-
+
That means that all of the Standard classes and functions (such as
string, vector<>, iostreams, and algorithms) will be freely available
and fully compliant. Programmers will no longer need to "roll their
own" nor be worried about platform-specific incompatabilities.
_________________________________________________________________
-
+
1.3 Who's in charge of it?
The libstdc++ project is contributed to by several developers all over
the world, in the same way as GCC (EGCS) or Linux. Benjamin Kosnik,
Gabriel Dos Reis, Nathan Myers, and Ulrich Drepper are the lead
maintainers of the CVS archive.
-
+
Development and discussion is held on the libstdc++ mailing list.
Subscribing to the list, or searching the list archives, is open to
everyone. You can read instructions for doing so on the [39]homepage.
If you have questions, ideas, code, or are just curious, sign up!
_________________________________________________________________
-
+
1.4 How do I get libstdc++?
The ninth (and latest) snapshot of libstdc++-v3 is [40]available via
ftp.
-
+
The [41]homepage has instructions for retrieving the latest CVS
sources, and for browsing the CVS sources over the web.
-
+
The subset commonly known as the Standard Template Library (chapters
23 through 25, mostly) is adapted from the SGI STL, which is also an
ongoing work.
_________________________________________________________________
-
+
1.5 When is libstdc++ going to be finished?
Nathan Myers gave the best of all possible answers in a Usenet article
asking this question: Sooner, if you help.
_________________________________________________________________
-
+
1.6 How do I contribute to the effort?
Here is [42]a page devoted to this topic. Subscribing to the mailing
is willing to help write documentation, for example, or has found a
bug in code that we all thought was working, is more than welcome!
_________________________________________________________________
-
+
1.7 What happened to libg++? I need that!
The most recent libg++ README states that libg++ is no longer being
actively maintained. It should not be used for new projects, and is
only being kicked along to support older code.
-
+
The libg++ was designed and created when there was no Standard to
provide guidance. Classes like linked lists are now provided for by
list<T> and do not need to be created by genclass. (For that matter,
templates exist now and are well-supported, whereas genclass (mostly)
predates them.)
-
+
There are other classes in libg++ that are not specified in the ISO
Standard (e.g., statistical analysis). While there are a lot of really
useful things that are used by a lot of people (e.g., statistics :-),
the Standards Committee couldn't include everything, and so a lot of
those "obvious" classes didn't get included.
-
+
Since libstdc++ is an implementation of the Standard Library, we have
no plans at this time to include non-Standard utilities in the
implementation, however handy they are. (The extensions provided in
entirely plausable that the "useful stuff" from libg++ might be
extracted into an updated utilities library, but nobody has stated
such a project yet.
-
+
(The [43]Boost site houses free C++ libraries that do varying things,
and happened to be started by members of the Standards Committee.
Certain "useful stuff" classes will probably migrate there.)
-
+
For the bold and/or desperate, the [44]GCC FAQ describes where to find
the last libg++ source.
_________________________________________________________________
-
+
1.8 What if I have more questions?
If you have read the README and RELEASE-NOTES files, and your question
information is available on the homepage (including how to browse the
list archives); to send to the list, use
[45]libstdc++@sources.redhat.com.
-
+
If you have a question that you think should be included here, or if
you have a question about a question/answer here, contact [46]Phil
Edwards or [47]Gabriel Dos Reis.
_________________________________________________________________
-
+
2.0 Installation
-
+
2.1 How do I install libstdc++-v3?
Complete instructions are not given here (this is a FAQ, not an
* If you plan on hacking around with the makefiles, you will need
the tools [48]autoconfand [49]automake.
* GNU Make is the only make that supports these makefiles.
-
+
The file [50]documentation.html provides a good overview of the steps
necessary to build, install, and use the library. Instructions for
configuring the library with new flags such as --enable-threads are
there also.
-
+
The top-level install.html and [51]RELEASE-NOTES files contain the
exact build and installation instructions. You may wish to browse
those files over CVSweb ahead of time to get a feel for what's
required. RELEASE-NOTES is located in the ".../docs/17_intro/"
directory of the distribution.
_________________________________________________________________
-
+
2.2 Is this a drop-in replacement for the libstdc++ that's shipped with g++?
Yes, as of 2.90.8, it is intended as such.
-
+
The installation instructions cover this in more detail, but replacing
the older library requires rebuilding some of the code that comes with
g++. You will need sources for the 2.95.2 compiler in order to build
this snapshot. Building the library on its own and then using -I/-L
will no longer work.
-
+
After the 2.90.8 snapshot, the library sources were integrated into
the compiler sources. Future releases of the compiler will ship with
libstdc++-v3.
_________________________________________________________________
-
+
2.3 What is this CVS thing that you keep mentioning?
The Concurrent Versions System is one of several revision control
free (beer), and very high quality. The [52]CVS entry in the GNU
software catalogue has a better description as well as a [53]link to
the makers of CVS.
-
+
The "anonymous client checkout" feature of CVS is similar to anonymous
FTP in that it allows anyone to retrieve the latest libstdc++ sources.
-
+
After the first of April, American users will have a "/pharmacy"
command-line option...
_________________________________________________________________
-
+
2.4 How do I know if it works?
libstdc++-v3 comes with its own testsuite. You do not need to actually
install the library ("gmake install") to run the testsuite.
-
+
To run the testsuite on the library after building it, use "gmake
check" while in your build directory. To run the testsuite on the
library after building and installing it, use "gmake check-install"
instead.
-
+
The testsuite subdirectory in your build directory will then contain
three files of the form YYYYMMDD-mkcheck*.txt. One of them
(-mkcheck.txt itself) contains the results of the tests; this can be
mailed to the list. The other files (-mkchecklog.txt and
-mkcheckfiles.txt) contain messages from the compiler while building
the test programs, and a list of the tests to be run, respectively.
-
+
If you are using the libgcc.a-rebuilding method to enable std:: you
might find that the testsuite starts dying with nasty linker errors.
This is symptomatic of the rebuilt libgcc.a not being installed; the
previous one is still in use.
-
+
If you find bugs in the testsuite programs themselves, or if you think
of a new test program that should be added to the suite, please write
up your idea and send it to the list!
_________________________________________________________________
-
+
3.0 Platform-Specific Issues
-
+
3.1 Can libstdc++-v3 be used with <my favorite compiler>?
Probably not. Yet.
-
+
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
(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.
-
+
Since the goal of ISO Standardization is for all C++ implementations
to be able to share code, the final libstdc++ should, in theory, be
useable under any ISO-compliant compiler. It will still be targeted
and optimized for GCC/g++, however.
_________________________________________________________________
-
+
3.2 Building under Cygwin hangs/explodes!?
Sometimes, yes. You're probably in the middle of generating the
numeric_limits specializations when it hangs, right? Thought so...
-
+
The <limits> header and its associated library code are
platform-specific. These files get generated from scratch during
installation, and it is this generator that is hanging. More
specifically, the only sure way to determine what the
numeric_limits<T>::traps boolean should be is to actually divide by
zero and see if it is trapped or not.
-
+
Under NT, this will occasionally just hang. On those occasions when
the test does not hang, the zero-division is in fact trapped. That
doesn't prevent hanging elsewhere.
-
+
You have two options. You can get a newer cygwin1.dll (see the Cygwin
paragraph in the [54]installation instructions). Or you can get a
prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from
Mumit Khan's [55]Cygwin-related website.
_________________________________________________________________
-
+
4.0 Known Bugs and Non-Bugs
-
+
Note that this section can get rapdily outdated -- such is the nature
of an open-source project. For the latest information, join the
mailing list or look through recent archives. The RELEASE- NOTES and
BUGS files are generally kept up-to-date.
-
+
4.1 What works already?
This is a verbatim clip from the "Status" section of the RELEASE-NOTES
- group checking for num_get implemented.
- Many, many bug fixes.
_________________________________________________________________
-
+
4.2 Bugs in gcc/g++ (not libstdc++-v3)
This is by no means meant to be complete nor exhaustive, but mentions
when building the locale-related source files. This has been fixed
in GCC 2.95.
_________________________________________________________________
-
+
4.3 Bugs in the C++ language/lib specification
Yes, unfortunately, there are some. In a [56]message to the list,
concern the library. The list itself is [57]posted on his website.
Developers who are having problems interpreting the Standard may wish
to consult his notes.
-
+
For those people who are not part of the ISO Library Group (i.e.,
nearly all of us needing to read this page in the first place :-), a
public list of the library defects is occasionally published [58]here.
_________________________________________________________________
-
+
4.4 Things in libstdc++ that look like bugs
There are things which are not bugs in the compiler (4.2) nor the
language specification (4.3), but aren't really bugs in libstdc++,
either. Really!
-
+
The biggest of these is the quadzillions of warnings about the library
headers emitted when -Weffc++ is used. Making libstdc++
"-Weffc++-clean" is not a goal of the project, for a few reasons.
while the Standard Library isn't necessarily trying to be OO. There
are multiple solutions under discussion.
_________________________________________________________________
-
+
4.5 Aw, that's easy to fix!
If you have found a bug in the library and you think you have a
you should of course send the patch to our mailing list, not the GCC
mailing list. The libstdc++ [60]contributors' page also talks about
how to submit patches.
-
+
In addition to the description, the patch, and the ChangeLog entry, it
is a Good Thing if you can additionally create a small test program to
test for the presence of the bug that your patch fixes. Bugs have a
caught immediately by the [61]testsuite -- but only if such a test
exists.
_________________________________________________________________
-
+
5.0 Miscellaneous
-
+
5.1 string::iterator is not char*; vector<T>::iterator is not T*
If you have code that depends on container<T> iterators being
implemented as pointer-to-T, your code is broken.
-
+
While there are arguments for iterators to be implemented in that
manner, A) they aren't very good ones in the long term, and B) they
were never guaranteed by the Standard anyway. The type-safety achieved
by making iterators a real class rather than a typedef for T*
outweighs nearly all opposing arguments.
_________________________________________________________________
-
+
5.2 What's next after libstdc++-v3?
Hopefully, not much. The goal of libstdc++-v3 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.
-
+
The ISO Committee will meet periodically to review Defect Reports in
the C++ Standard. Undoubtably 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.2. Some of those changes are being
predicted by the library maintainers, and we add code to the library
based on what the current proposed resolution specifies.
-
+
The current libstdc++ contains extensions to the Library which must be
explicitly requested by client code (for example, the hash tables from
SGI). Other extensions may be added to libstdc++-v3 if they seem to be
"standard" enough. (For example, the "long long" type from C99.)
Bugfixes and rewrites (to improve or fix thread safety, for instance)
will of course be a continuing task.
-
+
[62]This question about the next libstdc++ prompted some brief but
interesting [63]speculation.
_________________________________________________________________
-
+
5.3 What about the STL from SGI?
The [64]STL from SGI is merged into libstdc++-v3 with changes as
necessary. Currently release 3.3 is being used. Changes in the STL
usually produce some weird bugs and lots of changes in the rest of the
libstd++ source as we scramble to keep up. :-)
-
+
In particular, string is not from SGI and makes no use of their "rope"
class (which is included as an optional extension), nor is valarray
and some others. Classes like vector<> are, however.
-
+
The FAQ for SGI's STL (one jump off of their main page) is recommended
reading.
_________________________________________________________________
-
+
5.4 Extensions and Backward Compatibility
Although you can specify -I options to make the preprocessor search
Extensions to the library have [65]their own page.
_________________________________________________________________
-
+
5.5 Compiling with "-fnew-abi"
The library mostly works if you compile it (and programs you link with
base optimization, to name a few. (Note that the new ABI may change
from one GCC snapshot to the next, so you would have to rebuild all
your libraries each time you get a new compiler snapshot.)
-
+
Towards the end of July 1999, this subject was brought up again on the
mailing list under a different name. The related [66]thread (by the
name HOWTO-honor-std) is very instructive. More info is at the end of
RELEASE-NOTES.
-
+
This functionality is now automated and turned on by default.
_________________________________________________________________
-
+
5.6 Is libstdc++-v3 thread-safe?
Quick answer: no, as of 2.90.8 (ninth snapshot), the library is not
appropriate for multithreaded access. The string class is MT-safe.
-
+
This is assuming that your idea of "multithreaded" is the same as
ours... The general question of multithreading and libstdc++-v3 is
addressed in the chapter-specific advice for [67]Library Introduction.
Threadsafe containers are covered in more detail in [68]the Received
Wisdom section on containers.
_________________________________________________________________
-
+
5.7 How do I get a copy of the ISO C++ Standard?
Copies of the full ISO 14882 standard are available on line via the
right [69]here. (And if you've already registered with them, clicking
this link will take you to directly to the place where you can [70]buy
the standard on-line.
-
+
Who is your country's member body? Visit the [71]ISO homepage and find
out!
_________________________________________________________________
-
+
Comments and suggestions are welcome, and may be sent to [72]Phil
Edwards or [73]Gabriel Dos Reis.
- $Id: index.html,v 1.5 2000/07/11 21:45:08 pme Exp $
+ $Id: index.html,v 1.6 2000/09/25 21:42:14 pme Exp $
References
1. http://sources.redhat.com/libstdc++/
2. http://sources.redhat.com/libstdc++/faq/index.html
- 3. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html
- 4. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_0
- 5. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_1
- 6. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_2
- 7. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_3
- 8. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_4
- 9. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_5
- 10. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_6
- 11. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_7
- 12. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_8
- 13. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_0
- 14. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_1
- 15. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_2
- 16. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_3
- 17. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4
- 18. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#3_0
- 19. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#3_1
- 20. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#3_2
- 21. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_0
- 22. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_1
- 23. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_2
- 24. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_3
- 25. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_4
- 26. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_5
- 27. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_0
- 28. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_1
- 29. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_2
- 30. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_3
- 31. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_4
- 32. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_5
- 33. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_6
- 34. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_7
+ 3. ../index.html
+ 4. ../faq/index.html#1_0
+ 5. ../faq/index.html#1_1
+ 6. ../faq/index.html#1_2
+ 7. ../faq/index.html#1_3
+ 8. ../faq/index.html#1_4
+ 9. ../faq/index.html#1_5
+ 10. ../faq/index.html#1_6
+ 11. ../faq/index.html#1_7
+ 12. ../faq/index.html#1_8
+ 13. ../faq/index.html#2_0
+ 14. ../faq/index.html#2_1
+ 15. ../faq/index.html#2_2
+ 16. ../faq/index.html#2_3
+ 17. ../faq/index.html#2_4
+ 18. ../faq/index.html#3_0
+ 19. ../faq/index.html#3_1
+ 20. ../faq/index.html#3_2
+ 21. ../faq/index.html#4_0
+ 22. ../faq/index.html#4_1
+ 23. ../faq/index.html#4_2
+ 24. ../faq/index.html#4_3
+ 25. ../faq/index.html#4_4
+ 26. ../faq/index.html#4_5
+ 27. ../faq/index.html#5_0
+ 28. ../faq/index.html#5_1
+ 29. ../faq/index.html#5_2
+ 30. ../faq/index.html#5_3
+ 31. ../faq/index.html#5_4
+ 32. ../faq/index.html#5_5
+ 33. ../faq/index.html#5_6
+ 34. ../faq/index.html#5_7
35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz
- 36. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/DESIGN
+ 36. ../17_intro/DESIGN
37. http://gcc.gnu.org/
38. http://gcc.gnu.org/gcc-2.95/buildstat.html
- 39. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html
+ 39. ../index.html
40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz
- 41. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html
- 42. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html
+ 41. ../index.html
+ 42. ../17_intro/contribute.html
43. http://www.boost.org/
44. http://gcc.gnu.org/fom_serv/cache/33.html
45. mailto:libstdc++@sources.redhat.com
46. mailto:pme@sources.redhat.com
- 47. mailto:gdr@egcs.cygnus.com
+ 47. mailto:gdr@gcc.gnu.org
48. http://sources.redhat.com/autoconf/
49. http://sources.redhat.com/automake/
- 50. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/documentation.html
- 51. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/RELEASE-NOTES
+ 50. ../documentation.html
+ 51. ../17_intro/RELEASE-NOTES
52. http://www.gnu.org/software/cvs/cvs.html
53. http://www.cyclic.com/
- 54. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/install.html
+ 54. ../install.html
55. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html
- 56. file://localhost/ml/libstdc++/1998/msg00006.html
+ 56. http://sources.redhat.com/ml/libstdc++/1998/msg00006.html
57. http://www.cantrip.org/draft-bugs.txt
58. http://anubis.dkuug.dk/jtc1/sc22/wg21/
59. http://gcc.gnu.org/contribute.html
- 60. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html
- 61. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4
+ 60. ../17_intro/contribute.html
+ 61. ../faq/index.html#2_4
62. http://sources.redhat.com/ml/libstdc++/1999/msg00080.html
63. http://sources.redhat.com/ml/libstdc++/1999/msg00084.html
64. http://www.sgi.com/Technology/STL/
- 65. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/ext/howto.html
- 66. file://localhost/ml/libstdc++/1999-q3/msg00066.html
+ 65. ../ext/howto.html
+ 66. http://sources.redhat.com/ml/libstdc++/1999-q3/msg00066.html
67. http://sources.redhat.com/libstdc++/17_intro/howto.html#3
68. http://sources.redhat.com/libstdc++/23_containers/howto.html
69. http://www.ansi.org/
70. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
71. http://www.iso.ch/
72. mailto:pme@sources.redhat.com
- 73. mailto:gdr@egcs.cygnus.com
+ 73. mailto:gdr@gcc.gnu.org
projects / gcc.git / commitdiff