"Joseph S. Myers" <jos...@codesourcery.com> writes: > Why do a great many targets disable libgcj by default in the toplevel > configure.ac?
I believe that it's just a hack: libgcj doesn't build on the target, but gcc/java does. Disabling libgcj lets the gcc configure/make complete in a natural way. unsupported_languages is a clearly superior approach, but it postdates many of the cases in which libgcj is added to noconfigdirs. Ian
