severity 14685 minor
thanks
On 06/21/2013 10:19 PM, Werner LEMBERG wrote:
[automake 1.14]
[erroneously sent to the `automake' list]
It seems that there are problems if AC_CONFIG_MACRO_DIR contains more
than a single directory.
That's because AC_CONFIG_MACRO_DIR (provided by Autoconf)
That's because AC_CONFIG_MACRO_DIR (provided by Autoconf) is only
meant to accept one directory as its argument. For two or more
dirs, you should use AC_CONFIG_MACRO_DIRS instead (which BTW also
works if only one dir is given, so I'd suggest you to
unconditionally prefer it over
On 06/22/2013 09:44 AM, Werner LEMBERG wrote:
That's because AC_CONFIG_MACRO_DIR (provided by Autoconf) is only
meant to accept one directory as its argument. For two or more
dirs, you should use AC_CONFIG_MACRO_DIRS instead (which BTW also
works if only one dir is given, so I'd suggest you
Hi Diego, thanks for chiming in.
On 06/22/2013 12:19 PM, Diego Elio Pettenò wrote:
Hi Werner,
AC_CONFIG_MACRO_DIR expects a single directory (it's used by among other
libtool to put its m4 files).
AC_CONFIG_MACRO_DIRS is the one you want to use (plural form).
HTH
I think you've
Hi Werner,
AC_CONFIG_MACRO_DIR expects a single directory (it's used by among other
libtool to put its m4 files).
AC_CONFIG_MACRO_DIRS is the one you want to use (plural form).
HTH
Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog.flameeyes.eu/
On Fri, Jun 21, 2013 at 7:27
Hi Diego, thanks for chiming in.
On 06/22/2013 12:19 PM, Diego Elio Pettenò wrote:
Hi Werner,
AC_CONFIG_MACRO_DIR expects a single directory (it's used by among other
libtool to put its m4 files).
AC_CONFIG_MACRO_DIRS is the one you want to use (plural form).
HTH
I think you've
Hi all,
Stefano what is the current situation/plan for the stuff that was
deprecated and then undeprecated between automake 1.13 and 1.14?
I refer in particular to AM_PROG_MKDIR_P, AM_PROG_CC_STDC and
AM_CONFIG_HEADER macros, and the INCLUDES variable.
Are they planned for removal in 2.0 now?
On 06/22/2013 12:42 PM, Diego Elio Pettenò wrote:
Hi all,
Hi Diego.
Stefano what is the current situation/plan for the stuff that was
deprecated
Alas, it wasn't deprecated, but abruptly removed. That was the
real problem. The deprecations are still there, but are non-fatal
warnings instead
