Re: [PATCH 1/4] configure.ac: Define AM_PROG_AR for automake 1.11

Could the commit message say something about what exactly this fixes?

And why do we suddenly have an issue with a four year old version of automake?
Latest one is 1.14.

Somehow this feels wrong to me.

And the docs for AM_PROG_AR don't help either:

You must use this macro when you use the archiver in your project, if you want
support for unusual archivers such as Microsoft lib. The content of the optional
argument is executed if the archiver interface is not recognized; the default
action is to abort configure with an error message.


So, more commit message, please. I don't get it.

On 09.07.2014 03:13, Bryce W. Harrington wrote:
> Signed-off-by: Bryce Harrington <[email protected]>
> ---
>  configure.ac |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configure.ac b/configure.ac
> index 04479ff..66a8558 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -15,6 +15,7 @@ AC_CHECK_HEADERS([unistd.h sys/ioctl.h])
>  
>  AM_INIT_AUTOMAKE([1.11 foreign -Wall no-define no-dist-gzip dist-xz])
>  AM_SILENT_RULES([yes])
> +m4_ifdef([AM_PROG_AR], [AM_PROG_AR]) dnl Workaround for Automake 1.11
>  
>  # Initialize libtool
>  LT_PREREQ([2.2])
> 


-- 
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?" -- A. P. J.
-- 
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo