"Joseph S. Myers" <[EMAIL PROTECTED]> writes: > 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).
Good point. Ian
