On Thu, 19 Jun 2008, Ian Lance Taylor wrote: > Yes. I'm working around that for now by editing toplev.h, to avoid > pushing libcpp and libiberty to C++ right away.
I'm not convinced there's much value in building libiberty as C++ for GCC, given that it needs to remain buildable as C for now for the other projects using it and those projects may be built along with GCC in a combined tree (so sharing a single build of libiberty for the host). Much the same applies to libdecnumber, shared with GDB (and externally maintained). (I can however see the potential use of a library of C++ infrastructure shared between any C++ host tools in GCC and src, but think that would best be kept separate from libiberty. Much of libiberty could probably do with being replaced by, or merged into, gnulib anyway.) -- Joseph S. Myers [EMAIL PROTECTED]
