This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
_GLIBCPP_FULLY_COMPLIANT_HEADERS: Why not turned on?
- To: libstdc++ at gcc dot gnu dot org
- Subject: _GLIBCPP_FULLY_COMPLIANT_HEADERS: Why not turned on?
- From: Jeffrey Oldham <oldham at codesourcery dot com>
- Date: Wed, 14 Feb 2001 14:24:00 -0800
- Cc: oldham at codesourcery dot com
- Reply-to: oldham at codesourcery dot com
Why is the definition of _GLIBCPP_FULLY_COMPLIANT_HEADERS commented
out in libstdc++-v3/include/bits/c++config? The library should be
configured to obey the C++ standard. If a user wants better
performance, some non-default configuration switch should permit
faster compilation time.
By the way, without defining _GLIBCPP_FULLY_COMPLIANT_HEADERS,
basic_stringbuf's pbackfail() and overflow() are not defined even when
used with "char" template parameters.
/home/oldham/pooma/pooma-2.3.0/lib/LINUXgxx/libpooma-gcc.a(Inform.cmpl.o)(.gnu.linkonce.d._ZTVSt15basic_stringbufIcSt11char_traitsIcESaIcEE+0x34): undefined reference to `std::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::pbackfail(unsigned)'
/home/oldham/pooma/pooma-2.3.0/lib/LINUXgxx/libpooma-gcc.a(Inform.cmpl.o)(.gnu.linkonce.d._ZTVSt15basic_stringbufIcSt11char_traitsIcESaIcEE+0x3c): undefined reference to `std::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::overflow(unsigned)'
collect2: ld returned 1 exit status
(Please correspond directly to my email address because I do not
subscribe to the libstdc++ email list.)
Thanks,
Jeffrey D. Oldham
oldham@codesourcery.com