Target library disabling at toplevel
Ian Lance Taylor
iant@google.com
Tue Mar 22 22:07:00 GMT 2011
"Joseph S. Myers" <joseph@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
More information about the Java
mailing list