Single ABI: C++11

[Cristian Morales Vega]

The configure script, because of GLIBCXX_ENABLE_LIBSTDCXX_DUAL_ABI and
GLIBCXX_DEFAULT_ABI, doesn't let you have a single ABI with it being
the C++11/new one. Is this on purpose? There is any problem I'm not
aware of with using only the C++11 ABI?

I understand there may be a desire to keep backwards compatibility,
but I am thinking about the case where you are building it for an
embedded device where the toolchain I create will be the only one to
ever be used to create binaries running on it. Since I only need one
ABI, why not to use the new one? (not that I have any specific problem
using the old one) What I need is to save space, so the dual ABI is
also not ideal.