Re: Unresolved references to __builtin functions building libgcj

["Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>]

 > From: Alexandre Oliva <aoliva@redhat.com>
 > 
 > On Oct 11, 2000, Bryce McKinlay <bryce@albatross.co.nz> wrote:
 > 
 > > Attempting to build libgcj with the latest compiler dies for me with the
 > > following link failure:
 > 
 > > ./.libs/libgcj.so: undefined reference to `__pure_virtual'
 > > ./.libs/libgcj.so: undefined reference to `terminate(void)'
 > > ./.libs/libgcj.so: undefined reference to `__builtin_vec_new'
 > > ./.libs/libgcj.so: undefined reference to `__builtin_new'
 > 
 > Same here.  That's probably because the C++-specific functions that
 > used to be in libgcc have moved to libstdc++ and libsupc++ (the latter
 > on v3 only?).

Seems to me that the fact that the move of the C++ bits breaks libgcj
would have been noticed (and perhaps fixed) prior to installation of
the relevant patch had libgcj been in the unified source tree and part
of the standard build process.

I'm raising this, not to be annoying :-), but because IIRC the libgcj
merge is one of the gcc-3.0 release criteria and I was wondering what
the state of this is.  Is anyone working on it?

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions