On Fri, Oct 16, 2009 at 11:38 PM, <richard@xxxxxxxxxxxxxxxx> wrote: > ...handle AC_CONFIG_SUBDIRS... > > I could live with "don't" I would dislike that because people could start to rely on such an information (in a few years when all configure scripts are updated) and would miss the recursive warnings (where the feature would be most helpful due to the bigger length of output). I think it should be reliable or not given at all. > or requiring configure.ac-writer intervention, > because this tends to cause spurious warnings if the sub-configure has > fewer options than top level (e.g. configure: WARNING: unrecognized > options: --with-wx-config, because I'm building 3rd-party sub-libraries > that don't need wxWidgets, but top level does, and needs the option to > find it's libraries). Does this mean recent autoconf versions generate "unrecognized options" warnings? I always thought that autoconf does NOT generate such warnings exactly because of recursive configures? Was this changed? (in this case this could make usage of AC_SUBDIRS even more difficult in practice and disencouradge people to use it - but I really love this feature; good for orthogonality [package/subpackage independence]). oki, Steffen _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
