> Or do we expect to switch vax to gcc3 when gcc 3.4 hits our tree?
   
   That's for the vax toolchain maintainer to answer to...  Last I
   recall there were problems related to shared libraries with the
   new gcc, but I'm possibly not up to date with respect to the
   status of that work.


if vax doesn't get ELF shlibs with GCC3 soon it is going to lose
the ability.  it's well beyond time to delete the old copy of GCC,
and i'm going to do that with the next GCC upgrade...


.mrg.