Cloning against 'libtool' because both automake and libtool need to be
fixed.

+++ This bug was initially created as a clone of Bug #1155273 +++

Description of problem:

During linking(?) 'ar' prints a few warnings like this:

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

Example:

libtool: link: ar cru .libs/liberrnostring.a .libs/liberrnostring_la-errnostring-gperf.o .libs/liberrnostring_la-errnostring.o 
ar: `u' modifier ignored since `D' is the default (see `U')

Version-Release number of selected component (if applicable):

binutils-2.24-23.fc22.aarch64

How reproducible:

100%

Steps to Reproduce:

Seems to happen when linking any static libs.

--- Additional comment from Nick Clifton on 2014-10-24 18:00:00 CEST ---

Hi Richard,

  The warning message is correct.  Deterministic archives do not store file timestamps, so the 'u' option to only replace newer files cannot work.  If you are able to modify the build machinery for your project you can fix the problem by either using "ar cr ..." or "ar crUu ..." depending upon whether you want to maintain the deterministic nature of the libraries or not.  (I recommend the former).

Cheers
  Nick

PS.  Deterministic libraries were made the default when the binutils rpm is built because of this BZ:

  bugzilla.redhat.com/show_bug.cgi?id=1124342

--- Additional comment from Richard W.M. Jones on 2014-10-24 18:02:19 CEST ---

Fair enough.  Maybe this is a bug in libtool/automake/whatever it
is that runs 'ar'?

--- Additional comment from Jakub Jelinek on 2014-10-24 18:10:25 CEST ---

I'd think ar cruv being used widely everywhere.  If the problem is just that you want *.a libraries packaged in the distro without timestamps/uids/gids in them, perhaps some rpm macro/script (like the brp-strip-comment-note etc.) that would remove that from the *.a files that are going to be packaged would be a better solution...

--- Additional comment from Jaroslav Reznik on 2015-03-03 17:23:23 CET ---

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

--- Additional comment from Nathaniel McCallum on 2015-03-26 19:20:57 CET ---

I think the proper place for this is automake. This is triggered by any automake library build.

--- Additional comment from Richard W.M. Jones on 2015-03-26 21:09:21 CET ---

Still happens in Rawhide.  Although I don't believe it causes any
actual problem.

--- Additional comment from Pavel Raiskup on 2015-03-27 09:21:24 CET ---

Automake/Libtool upstream discussion:
http://lists.gnu.org/archive/html/bug-automake/2015-03/msg00004.html
http://lists.gnu.org/archive/html/bug-libtool/2015-02/msg00014.html

--- Additional comment from Petr Pisar on 2015-04-28 14:29:10 CEST ---

I can see this warning even on x86_64 when building pcre-8.37 with these packages:

automake-1.15-1.fc22.noarch
libtool-2.4.6-4.fc23.x86_64
binutils-2.25-8.fc23.x86_64