GNU bug report logs - #11401
automake-1.12 (incorrectly?) complains about missing AM_PROG_AR

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11401 in the body.
You can then email your comments to 11401 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mike Frysinger <vapier <at> gentoo.org>
To: bug-automake <at> gnu.org
Subject: automake-1.12 (incorrectly?) complains about missing AM_PROG_AR
Date: Fri, 4 May 2012 01:25:57 -0400

[Message part 1 (text/plain, inline)]

consider this simple code base:
$ cat configure.ac
AC_PREREQ([2.63])
AC_INIT([foo], [0])
AM_INIT_AUTOMAKE([1.11 -Wall foreign])
AC_PROG_CC
LT_INIT
AC_OUTPUT(Makefile)

$ cat Makefile.am
lib_LTLIBRARIES = libfoo.la
libfoo_la_SOURCES = foo.c

$ touch foo.c

with automake-1.11.5, everything works great:
$ autoreconf -f -i
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

however, upgrade to automake-1.12, and it starts spitting this:
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
/usr/share/automake-1.12/am/ltlibrary.am: warning: 'libfoo.la': linking libtool libraries using a non-POSIX
/usr/share/automake-1.12/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac'
Makefile.am:1:   while processing Libtool library 'libfoo.la'

what gives ?
-mike

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 11401 <at> debbugs.gnu.org (full text, mbox):

From: Peter Rosin <peda <at> lysator.liu.se>
To: Mike Frysinger <vapier <at> gentoo.org>
Cc: 11401 <at> debbugs.gnu.org
Subject: Re: bug#11401: automake-1.12 (incorrectly?) complains about missing
	AM_PROG_AR
Date: Fri, 04 May 2012 09:20:10 +0200

Hi Mike!

On 2012-05-04 07:25, Mike Frysinger wrote:
> consider this simple code base:
> $ cat configure.ac
> AC_PREREQ([2.63])
> AC_INIT([foo], [0])
> AM_INIT_AUTOMAKE([1.11 -Wall foreign])
> AC_PROG_CC
> LT_INIT
> AC_OUTPUT(Makefile)
> 
> $ cat Makefile.am
> lib_LTLIBRARIES = libfoo.la
> libfoo_la_SOURCES = foo.c
> 
> $ touch foo.c
> 
> with automake-1.11.5, everything works great:
> $ autoreconf -f -i
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> 
> however, upgrade to automake-1.12, and it starts spitting this:
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> /usr/share/automake-1.12/am/ltlibrary.am: warning: 'libfoo.la': linking libtool libraries using a non-POSIX
> /usr/share/automake-1.12/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac'
> Makefile.am:1:   while processing Libtool library 'libfoo.la'
> 
> what gives ?

If you don't want *all* warnings, don't ask for *all* warnings :-)

It's in NEWS, from 1.12:

  - The warnings in the category 'extra-portability' are now enabled by
    '-Wall'.  In previous versions, one has to use '-Wextra-portability'
    to enable them.

which should be read in light of this from 1.11.2:

  - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
    'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
    This new macro is required for LIBRARIES and LTLIBRARIES when automake
    is run with -Wextra-portability and -Werror.

You can get rid of the warning with the following (but I have not actually
tested with your example):

AM_INIT_AUTOMAKE([1.11 -Wall -Wno-extra-portability foreign])

Cheers,
Peter

Message #11 received at 11401 <at> debbugs.gnu.org (full text, mbox):

From: Mike Frysinger <vapier <at> gentoo.org>
To: Peter Rosin <peda <at> lysator.liu.se>
Cc: 11401 <at> debbugs.gnu.org
Subject: Re: bug#11401: automake-1.12 (incorrectly?) complains about missing
	AM_PROG_AR
Date: Fri, 4 May 2012 15:19:49 -0400

[Message part 1 (text/plain, inline)]

On Friday 04 May 2012 03:20:10 Peter Rosin wrote:
> On 2012-05-04 07:25, Mike Frysinger wrote:
> > consider this simple code base:
> > $ cat configure.ac
> > AC_PREREQ([2.63])
> > AC_INIT([foo], [0])
> > AM_INIT_AUTOMAKE([1.11 -Wall foreign])
> > AC_PROG_CC
> > LT_INIT
> > AC_OUTPUT(Makefile)
> > 
> > $ cat Makefile.am
> > lib_LTLIBRARIES = libfoo.la
> > libfoo_la_SOURCES = foo.c
> > 
> > $ touch foo.c
> > 
> > with automake-1.11.5, everything works great:
> > $ autoreconf -f -i
> > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
> > and
> > libtoolize: rerunning libtoolize, to keep the correct libtool macros
> > in-tree.
> > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> > 
> > however, upgrade to automake-1.12, and it starts spitting this:
> > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
> > and
> > libtoolize: rerunning libtoolize, to keep the correct libtool macros
> > in-tree.
> > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> > /usr/share/automake-1.12/am/ltlibrary.am: warning: 'libfoo.la': linking
> > libtool libraries using a non-POSIX
> > /usr/share/automake-1.12/am/ltlibrary.am: archiver requires 'AM_PROG_AR'
> > in 'configure.ac'
> > Makefile.am:1:   while processing Libtool library 'libfoo.la'
> > 
> > what gives ?
> 
> If you don't want *all* warnings, don't ask for *all* warnings :-)

not my code base ;)

> It's in NEWS, from 1.12:
> 
>   - The warnings in the category 'extra-portability' are now enabled by
>     '-Wall'.  In previous versions, one has to use '-Wextra-portability'
>     to enable them.

ok, so the fact that it's warning via -Wall is new to 1.12, but the underlying 
issue (warning at all) is not

> which should be read in light of this from 1.11.2:
> 
>   - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
>     'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
>     This new macro is required for LIBRARIES and LTLIBRARIES when automake
>     is run with -Wextra-portability and -Werror.

imo, projects utilizing libtool shouldn't need to know this at all.  the whole 
point is to hide these esoteric details behind a layer and focus on the bits 
that projects actually care about -- what sources to put into libraries, 
etc...  so is the answer to update libtool to call AM_PROG_AR when it's 
available ?
-mike

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 11401 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Mike Frysinger <vapier <at> gentoo.org>
Cc: Peter Rosin <peda <at> lysator.liu.se>, 11401 <at> debbugs.gnu.org
Subject: Re: bug#11401: automake-1.12 (incorrectly?) complains about missing
	AM_PROG_AR
Date: Fri, 11 May 2012 13:37:55 +0200

On 05/04/2012 09:19 PM, Mike Frysinger wrote:
> On Friday 04 May 2012 03:20:10 Peter Rosin wrote:
>> On 2012-05-04 07:25, Mike Frysinger wrote:
>>>
>>> $ cat configure.ac
>>> AC_PREREQ([2.63])
>>> AC_INIT([foo], [0])
>>> AM_INIT_AUTOMAKE([1.11 -Wall foreign])
>>> AC_PROG_CC
>>> LT_INIT
>>> AC_OUTPUT(Makefile)
>>>
>>> $ cat Makefile.am
>>> lib_LTLIBRARIES = libfoo.la
>>> libfoo_la_SOURCES = foo.c
>>>
>>> with automake-1.11.5, everything works great, but with automake 1.12:
>>>
>>> $ autoreconf -f -i
>>>> ...
>>> ltlibrary.am: warning: 'libfoo.la': linking libtool libraries using a non-POSIX
>>> ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac'
>>> Makefile.am:1:   while processing Libtool library 'libfoo.la'
>>>
>>> what gives ?
>>
>> If you don't want *all* warnings, don't ask for *all* warnings :-)
> 
> not my code base ;)
> 
>> It's in NEWS, from 1.12:
>>
>>   - The warnings in the category 'extra-portability' are now enabled by
>>     '-Wall'.  In previous versions, one has to use '-Wextra-portability'
>>     to enable them.
> 
> ok, so the fact that it's warning via -Wall is new to 1.12, but the underlying 
> issue (warning at all) is not
>
Exactly.

>> which should be read in light of this from 1.11.2:
>>
>>   - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
>>     'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
>>     This new macro is required for LIBRARIES and LTLIBRARIES when automake
>>     is run with -Wextra-portability and -Werror.
> 
> imo, projects utilizing libtool shouldn't need to know this at all.  the whole 
> point is to hide these esoteric details behind a layer and focus on the bits 
> that projects actually care about -- what sources to put into libraries, 
> etc...  so is the answer to update libtool to call AM_PROG_AR when it's 
> available ?
>
It seems there might be consensus on this idea:

  <http://lists.gnu.org/archive/html/automake/2012-05/msg00012.html>

If it will turn out that is actually the case, I will close this bug report
(the discussion will likely continue on the bug-libtool list).  For now, let's
wait and see how things evolve.

Regards,
   Stefano

Message #17 received at 11401 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: 11401 <at> debbugs.gnu.org
Subject: moreinfo
Date: Sun, 22 Jul 2012 17:48:05 +0200

severity 11401 minor
tags 11401 + moreinfo
thanks

I'm tagging this bug with "more info required", because we're still
waiting to see how things will evolve on the Libtool side.

Regards,
  Stefano

Message #24 received at 11401 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Mike Frysinger <vapier <at> gentoo.org>
Cc: Libtool List <libtool <at> gnu.org>, Peter Rosin <peda <at> lysator.liu.se>,
	11401 <at> debbugs.gnu.org
Subject: Automake, Libtool and AM_PROG_AR (was: Re: bug#11401: automake-1.12
	(incorrectly?) complains about missing AM_PROG_AR)
Date: Wed, 21 Nov 2012 11:46:50 +0100

References:
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11401>
<http://lists.gnu.org/archive/html/automake/2012-05/msg00012.html>

On 05/11/2012 01:37 PM, Stefano Lattarini wrote:
> On 05/04/2012 09:19 PM, Mike Frysinger wrote:
>> On Friday 04 May 2012 03:20:10 Peter Rosin wrote:
>>> On 2012-05-04 07:25, Mike Frysinger wrote:
>>>>
>>>> $ cat configure.ac
>>>> AC_PREREQ([2.63])
>>>> AC_INIT([foo], [0])
>>>> AM_INIT_AUTOMAKE([1.11 -Wall foreign])
>>>> AC_PROG_CC
>>>> LT_INIT
>>>> AC_OUTPUT(Makefile)
>>>>
>>>> $ cat Makefile.am
>>>> lib_LTLIBRARIES = libfoo.la
>>>> libfoo_la_SOURCES = foo.c
>>>>
>>>> with automake-1.11.5, everything works great, but with automake 1.12:
>>>>
>>>> $ autoreconf -f -i
>>>>> ...
>>>> ltlibrary.am: warning: 'libfoo.la': linking libtool libraries using a non-POSIX
>>>> ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac'
>>>> Makefile.am:1:   while processing Libtool library 'libfoo.la'
>>>>
>>>> what gives ?
>>>
>>> If you don't want *all* warnings, don't ask for *all* warnings :-)
>>
>> not my code base ;)
>>
>>> It's in NEWS, from 1.12:
>>>
>>>   - The warnings in the category 'extra-portability' are now enabled by
>>>     '-Wall'.  In previous versions, one has to use '-Wextra-portability'
>>>     to enable them.
>>
>> ok, so the fact that it's warning via -Wall is new to 1.12, but the underlying 
>> issue (warning at all) is not
>>
> Exactly.
> 
>>> which should be read in light of this from 1.11.2:
>>>
>>>   - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
>>>     'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
>>>     This new macro is required for LIBRARIES and LTLIBRARIES when automake
>>>     is run with -Wextra-portability and -Werror.
>>
>> imo, projects utilizing libtool shouldn't need to know this at all.  the whole 
>> point is to hide these esoteric details behind a layer and focus on the bits 
>> that projects actually care about -- what sources to put into libraries, 
>> etc...  so is the answer to update libtool to call AM_PROG_AR when it's 
>> available ?
>>
> It seems there might be consensus on this idea:
> 
>   <http://lists.gnu.org/archive/html/automake/2012-05/msg00012.html>
> 
> If it will turn out that is actually the case, I will close this bug report
> (the discussion will likely continue on the bug-libtool list).  For now, let's
> wait and see how things evolve.
>
Any news on this?  Since it doesn't seem a big deal anyway, unless I hear
something new in a few days, I'll go ahead and close the bug report, leaving
the matter in the hands of the libtoolers.

Regards,
  Stefano

Message #29 received at 11401-done <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Mike Frysinger <vapier <at> gentoo.org>
Cc: Libtool List <libtool <at> gnu.org>, Peter Rosin <peda <at> lysator.liu.se>,
	11401-done <at> debbugs.gnu.org
Subject: Re: Automake, Libtool and AM_PROG_AR
Date: Mon, 26 Nov 2012 13:37:58 +0100

On 11/21/2012 11:46 AM, Stefano Lattarini wrote:
> References:
> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11401>
> <http://lists.gnu.org/archive/html/automake/2012-05/msg00012.html>
> 
> Any news on this?  Since it doesn't seem a big deal anyway, unless I hear
> something new in a few days, I'll go ahead and close the bug report, leaving
> the matter in the hands of the libtoolers.
>
I've closed this report now.

Regards,
  Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.