On 04/27/2011 05:50 PM, Joseph S. Myers wrote:
Continuing the toplevel cleanups separating the cases disabling different subdirectories - on the basis that eventually this information should come from the subdirectories, and that as previously discussed much of the default disabling of ${libgcj} doesn't actually make sense - this patch separates the Java-and-${libgcj}-disabling cases out from the rest of the directory-disabling cases.This patch deliberately keeps the case structure the same to make it clear it does not change the set of disabled directories at all - thus there are now empty cases in both the old and the new case statements. These are intended to be cleaned up in subsequent patches. (Removing an empty case is not automatically obvious, since it may cause a later case such as *-*-linux* | *-*-gnu* | *-*-k*bsd*-gnu | *-*-kopensolaris*-gnu or *-*-* to be active instead. In many cases they can be removed, because the combination that would activate the other case is not meaningful or because it doesn't matter what the Java configuration is for targets that have been removed from or never supported in GCC - but I prefer to keep such removals separate.) OK to commit? 2011-04-27 Joseph Myers<jos...@codesourcery.com> * configure.ac: Separate cases disabling Java and Java libraries from general case over targets. * configure: Regenerate.
Ok. Paolo
