[RFH] libstdc++ compatibility configured with different allocators

[Matthias Klose <doko@cs.tu-berlin.de>]

Debian does configure libstdc++ with --enable-libstdcxx-allocator=mt ,
based on discussions in April 2004 on libstdc++.  Fedora used that
configuration as well, and in July 2005 went back to configure
libstdc++ using the default (new) allocator due to outstanding
problems with the mt allocator.  I got the advise to change this
configuration in Debian as well.  The symbols exported by libstdc++
for both configurations are the same, however it has an effect on
symbols exported by libraries which use containers (using an
allocator) from the template headers (seen in about 1/4 of the Debian
packages depending on libstdc++6).  These packages having references
to the mt_alloc symbols have to be rebuilt, but is it necessay to
rebuild the remaing 3/4 packages as well?  Questions raised in [1]
were about a change in the internal representation of std::string
(which I cannot see), or some other template instantiation provided by
libstdc++.

Thanks, Matthias

[1] http://lists.debian.org/debian-gcc/2005/11/msg00115.html