From: Stefano Lattarini Date: Mon, 28 May 2012 11:52:34 +0000 (+0200) Subject: news: support for configure.in will be dropped in future automake versions X-Git-Tag: v1.12.1~6 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=abc3d3d1c4acb4e8f83c948ee7b2ce51c6022291;p=platform%2Fupstream%2Fautomake.git news: support for configure.in will be dropped in future automake versions The use of configure.in as Autoconf input has been deprecated for a very long time in the Autoconf documentation, and the next version of Autoconf (2.70) will start warning about it ar runtime as well (see commit 'v2.69-4-g560f16b' or 2012-05-23, "general: deprecate 'configure.in' as autoconf input", in the Autoconf's git repository). * NEWS (Future backward-incompatibilities): Update. Signed-off-by: Stefano Lattarini --- diff --git a/NEWS b/NEWS index 944f7f9..4046758 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,11 @@ New in 1.12.1: * WARNING: Future backward-incompatibilities! + - Starting from either the next minor version (1.12.2) or the next major + version (1.13), Automake will start warning if 'configure.in' is used + instead of 'configure.ac' as the Autoconf input. Future versions of + Automake will drop support for 'configure.in' altogether. + - Autoconf 2.65 or later will be required by the next major Automake version (1.13). Until now, Automake has required Autoconf version 2.62 or later.