GNU bug report logs - #30118
How to force using ARFLAGS = cr instead of "cru" to overcome the warning : ar: `u' modifier ignored since `D' is the default (see `U')

Previous Next

To reply to this bug, email your comments to 30118 AT debbugs.gnu.org.

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

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

From:  . <d3m0nkingx <at> gmail.com>
To: bug-libtool <at> gnu.org
Subject: How to force using ARFLAGS = cr instead of "cru" to overcome the
 warning : ar: `u' modifier ignored since `D' is the default (see `U')
Date: Sun, 14 Jan 2018 22:04:21 -0500

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

*The environment:*

 host-triplet:   x86_64-pc-linux-gnu
       shell:          /bin/bash
       compiler:       gcc
       compiler flags: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security
       linker:         /usr/bin/ld -m elf_x86_64 (gnu? yes)
       version:        libtool (GNU libtool) 2.4.6
       automake:       automake (GNU automake) 1.15
       autoconf:       autoconf (GNU Autoconf) 2.69


*The Project being built:*

https://github.com/dogecoin/dogecoin.git


*The Error:*

ar: `u' modifier ignored since `D' is the default (see `U')


*The temporary solution:*

So I've basically come to the point that to make this work you have to
modify two files and change "cru" to "cr" in them :

/usr/share/aclocal/libtool.m4

and

/usr/share/libtool/configure


then rerun ./autogen.sh and ./configure

Additionally add to make command line::

make ARFLAGS="cr" AR_FLAGS="cr"




====================
This affectively suppresses the warning from appearing, but it's not a
clean way to make this work. Could you please assist with this matter thank
you. Also I've looked into the libtool repository :  git://
git.savannah.gnu.org/libtool.git  and saw a NEWS file stating:

* New features:

  - Libtool script now supports (configure-time and runtime) ARFLAGS
    variable, which obsoletes AR_FLAGS.  This is due to naming conventions
    among other *FLAGS and to be consistent with Automake's ARFLAGS.

  - Gnulib testsuite is enabled and run during 'make check'.

** Important incompatible changes:

  - Libtool changed ARFLAGS/AR_FLAGS default from 'cru' to 'cr'.


However, it's unclear how the configure-time and runtime ARFLAGS var should
be set. Various options have been tried in the configure.ac and Makefile.am
files, but nothing worked.

Hope to hear from you soon on a viable option here. Thank you in advance
for your attention to this matter.

Regards,


d3m0nkingx <at> gmail.com

P.S. This is something many crypto projects have in their code base that is
throwing this warning including Bitcoin itself. Would be nice to make this
a permanent fix.

[Message part 2 (text/html, inline)]

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

From: Peter Rosin <peda <at> lysator.liu.se>
To: "." <d3m0nkingx <at> gmail.com>, 30118 <at> debbugs.gnu.org
Subject: Re: bug#30118: How to force using ARFLAGS = cr instead of "cru" to
 overcome the warning : ar: `u' modifier ignored since `D' is the default (see
 `U')
Date: Mon, 15 Jan 2018 17:13:06 +0100

On 2018-01-15 04:04,  . wrote:
>  Also I've looked into the libtool repository :  git://git.savannah.gnu.org/libtool.git <http://git.savannah.gnu.org/libtool.git>  and saw a NEWS file stating:
> 
> * New features:
> 
>   - Libtool script now supports (configure-time and runtime) ARFLAGS
>     variable, which obsoletes AR_FLAGS.  This is due to naming conventions
>     among other *FLAGS and to be consistent with Automake's ARFLAGS.
> 
>   - Gnulib testsuite is enabled and run during 'make check'.
> 
> ** Important incompatible changes:
> 
>   - Libtool changed ARFLAGS/AR_FLAGS default from 'cru' to 'cr'.
> 
> 
> However, it's unclear how the configure-time and runtime ARFLAGS var should be set. Various options have been tried in the configure.ac <http://configure.ac> and Makefile.am files, but nothing worked. 
> 
> Hope to hear from you soon on a viable option here. Thank you in advance for your attention to this matter. 

These NEWS entries (and corresponding changes) are not yet in any released version
of Libtool, they are only committed to the source repo. There seems to be little
progress on actually making a new Libtool release, so you're probably better off
not holding your breath...

Cheers,
Peter

Previous Next

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