From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#40459: Non-reproducible behaviour in libtool < 2.2.7b bootstrapped ltmain.sh Date: Mon, 06 Apr 2020 11:21:22 +0200 Message-ID: <87sghhdl65.fsf@gnu.org> References: <16D3F058-8D50-48AD-BAC4-A2124A49A40B@carldong.me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:41849) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jLNxF-0006zz-UO for bug-guix@gnu.org; Mon, 06 Apr 2020 05:22:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jLNxC-0000DS-Uo for bug-guix@gnu.org; Mon, 06 Apr 2020 05:22:05 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:35617) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jLNxC-0000DK-RS for bug-guix@gnu.org; Mon, 06 Apr 2020 05:22:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jLNxB-000628-NZ for bug-guix@gnu.org; Mon, 06 Apr 2020 05:22:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <16D3F058-8D50-48AD-BAC4-A2124A49A40B@carldong.me> (Carl Dong's message of "Sun, 05 Apr 2020 21:31:27 +0000") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Carl Dong Cc: 40459@debbugs.gnu.org Hello! Carl Dong skribis: > While investigating a libstdc++.a reproducibility issue, I found that > libtool prior to 74c8993c (first included in version 2.2.7b, link: > https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=3D74c8993c178a13= 86ea5e2363a01d919738402f30) > did not sort find output. Right, good ol=E2=80=99days! > It seems that many packages (including all released gcc versions so > far) are bootstrapped with a libtool < 2.2.7b. Ouch, I didn=E2=80=99t expect this. > There are probably many ways to approach this, and I propose that we coul= d simply use a somewhat strict regex find and replace on ltmain.sh. Yes, we could add a standard build phase to do that. We just need to make sure we get the regexp right so it doesn=E2=80=99t break newer =E2=80= =98ltmain.sh=E2=80=99 scripts. WDYT? Ludo=E2=80=99.