From debbugs-submit-bounces@debbugs.gnu.org Sun Jan 14 22:13:26 2018 Received: (at submit) by debbugs.gnu.org; 15 Jan 2018 03:13:27 +0000 Received: from localhost ([127.0.0.1]:56557 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eavDC-00052V-Gy for submit@debbugs.gnu.org; Sun, 14 Jan 2018 22:13:26 -0500 Received: from eggs.gnu.org ([208.118.235.92]:37264) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eav56-0004pN-5D for submit@debbugs.gnu.org; Sun, 14 Jan 2018 22:05:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eav4z-00082u-NB for submit@debbugs.gnu.org; Sun, 14 Jan 2018 22:04:59 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org X-Spam-Level: * X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_05,FREEMAIL_FROM, HTML_MESSAGE,T_DKIM_INVALID,URIBL_BLACK autolearn=disabled version=3.3.2 Received: from lists.gnu.org ([2001:4830:134:3::11]:40708) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eav4z-00082g-KS for submit@debbugs.gnu.org; Sun, 14 Jan 2018 22:04:57 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56457) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eav4y-0005FR-3p for bug-libtool@gnu.org; Sun, 14 Jan 2018 22:04:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eav4v-00080m-H3 for bug-libtool@gnu.org; Sun, 14 Jan 2018 22:04:56 -0500 Received: from mail-qt0-x22b.google.com ([2607:f8b0:400d:c0d::22b]:40971) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eav4v-00080d-9z for bug-libtool@gnu.org; Sun, 14 Jan 2018 22:04:53 -0500 Received: by mail-qt0-x22b.google.com with SMTP id i40so12626344qti.8 for ; Sun, 14 Jan 2018 19:04:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=RXxNQaUqSNyEE6BWjOp1fFmYECn7atrx5QMbSQmiYAQ=; b=iZj8dIpJf7I8gs6zNCfxjz0mRziu6jRH8vQFTly0/PfSZwodtPfxhcG2WiSuw/1ZXG SEuMYQ7grEpg/X6jUKtPJ2P30I7jd15pj1k8LaR83fRVxtEYxgQQiB2HNLxIzd42bxhT uBrmV6AvjnDofxtKju9tzs0n02WNf4anpTcrUWQsRh7P6wVGnmRVEo/CVRtfL27ZdG+v +iUfLfxBqKE134x/jwpQVjJvWm6c5Q0f1GUzgOVoJCt4Hhp9LfFJVACx2CkF7hF7xKZJ 9mkUMc32J5+/7wNMR6esRTzHFLxbK7eTZBbruNVudcz7QmbnTLU+EJypPgZwX23/3sM4 VETQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=RXxNQaUqSNyEE6BWjOp1fFmYECn7atrx5QMbSQmiYAQ=; b=IdRviBOTzFILwCSQ5G8m+5A/micYg6kz0CRpxJNRXbMhh8q5KipRt+QsHG0QoR1qkh hTY/oZYx7Fvoubd46R4jRZmmWdYL+iU5Ve1lk67glUyDjtfBdwWMpQon+2oC7XDOnwZ8 YzCsZzJgmwMcdr+XQ3pnUJqHDZZcFdkZz4xVZ+oEM745aFR4PbtjjBTfyiaJsgIy/s+h KhT+K+yPnsfZxeGXgQZJXCsaXnD3IVNN60Kqr3LvY6GinrenOUsc48RuOwSrhB9VecxA 3nE48F755WtO7i6rVXHnZF+nh/ZXDEvwXBizH2zNHjIiZj521XQAeyrPnRn+KQDxI54U tKWA== X-Gm-Message-State: AKwxytdi1TrRT/xQChw0bOz76mF/qBhzzYgtlYuprNWBPrJfyQjIsyk2 E2x4BookwnGgjUXsEe+lJwkO2DnrUXOB9fYh5P94RA== X-Google-Smtp-Source: ACJfBotv+4GPY2czzHTa5NlCbrsNcyIHIWbJbWkPljiA4wp9NRHSIunQeg9+LifsTzPYKzc8k/xG6l3WN62rOpEZ460= X-Received: by 10.237.58.102 with SMTP id n93mr30015165qte.49.1515985492162; Sun, 14 Jan 2018 19:04:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.25.132 with HTTP; Sun, 14 Jan 2018 19:04:21 -0800 (PST) From: =?UTF-8?B?wqAu?= Date: Sun, 14 Jan 2018 22:04:21 -0500 Message-ID: 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') To: bug-libtool@gnu.org Content-Type: multipart/alternative; boundary="001a113f458cbebecf0562c7e001" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 2001:4830:134:3::11 X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Sun, 14 Jan 2018 22:13:25 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) --001a113f458cbebecf0562c7e001 Content-Type: text/plain; charset="UTF-8" *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@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. --001a113f458cbebecf0562c7e001 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The environment:

=C2=A0host-triplet:=C2=A0 =C2=A0x86_64-pc-linux-gnu
=C2=A0 =C2=A0 = =C2=A0 =C2=A0shell:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /bin/bash
=C2=A0 =C2= =A0 =C2=A0 =C2=A0compiler:=C2=A0 =C2=A0 =C2=A0 =C2=A0gcc
=C2=A0 =C2=A0 =C2= =A0 =C2=A0compiler flags: -g -O2 -fstack-protector-strong -Wformat -Werror= =3Dformat-security
=C2=A0 =C2=A0 =C2=A0 =C2=A0linker:=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0/usr/bin/ld -m elf_x86_64 (gnu? yes)
=C2=A0 =C2=A0 =C2=A0 =C2= =A0version:=C2=A0 =C2=A0 =C2=A0 =C2=A0 libtool (GNU libtool) 2.4.6
=C2=A0 = =C2=A0 =C2=A0 =C2=A0automake:=C2=A0 =C2=A0 =C2=A0 =C2=A0automake (GNU autom= ake) 1.15
=C2=A0 =C2=A0 =C2=A0 =C2=A0autoconf:=C2=A0 =C2=A0 =C2=A0 =C2=A0aut= oconf (GNU Autoconf) 2.69


The Project being built:



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 mo= dify two files and change "cru" to "cr" in them :

/usr/share/aclocal/libtool.m4

and

/usr/share/libtool/configure

then rerun=C2=A0./autogen.sh and ./configure

Additionally add to make c= ommand line::

make ARFLA= GS=3D"cr" AR_FLAGS=3D"cr"




=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This a= ffectively 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 :=C2=A0=C2=A0git://git.savannah.gnu.org/libtool.git=C2= =A0=C2=A0and saw a NEWS file stating:
<= div>
* New features:

=C2=A0 - Libtool script now supports (configure-time = and runtime) ARFLAGS
=C2=A0 =C2=A0 variable, which obsoletes AR_F= LAGS.=C2=A0 This is due to naming conventions
=C2=A0 =C2=A0 among= other *FLAGS and to be consistent with Automake's ARFLAGS.
<= br>
=C2=A0 - Gnulib testsuite is enabled and run during 'make= check'.

** Important incompatible changes:

=C2=A0 - Libtool changed ARFLAGS/AR_FLAGS default fr= om '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.= =C2=A0

Hope to hear from you = soon on a viable option here. Thank you in advance for your attention to th= is matter.=C2=A0
=
Regards,=C2= =A0



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.
--001a113f458cbebecf0562c7e001-- From debbugs-submit-bounces@debbugs.gnu.org Mon Jan 15 11:13:13 2018 Received: (at 30118) by debbugs.gnu.org; 15 Jan 2018 16:13:13 +0000 Received: from localhost ([127.0.0.1]:57672 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eb7Np-00066n-IE for submit@debbugs.gnu.org; Mon, 15 Jan 2018 11:13:13 -0500 Received: from mail.lysator.liu.se ([130.236.254.3]:44625) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eb7No-00066c-7U for 30118@debbugs.gnu.org; Mon, 15 Jan 2018 11:13:12 -0500 Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 3F46840021; Mon, 15 Jan 2018 17:13:10 +0100 (CET) Received: from [192.168.13.3] (c-17f4e255.26241707-0-68616c6d7374616473746164736e6174.cust.bredbandsbolaget.se [85.226.244.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 08EEA40020; Mon, 15 Jan 2018 17:13:09 +0100 (CET) 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') To: "." , 30118@debbugs.gnu.org References: From: Peter Rosin Message-ID: Date: Mon, 15 Jan 2018 17:13:06 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 30118 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) On 2018-01-15 04:04,  . wrote: > 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.  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