From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3254 invoked by alias); 20 Sep 2017 17:24:00 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 3232 invoked by uid 89); 20 Sep 2017 17:23:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-20.8 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,KAM_INFOUSMEBIZ,KAM_LAZY_DOMAIN_SECURITY,RDNS_DYNAMIC,URIBL_SBL autolearn=ham version=3.3.2 spammy=Administrator, Hx-languages-length:1993, H*M:info, H*F:D*info X-Spam-User: qpsmtpd, 2 recipients X-HELO: void-ptr.info Received: from pppoe.185.44.68.223.lanport.ru (HELO void-ptr.info) (185.44.68.223) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 20 Sep 2017 17:23:58 +0000 Received: from ptr by void-ptr.info with local (Exim 4.72) (envelope-from ) id 1duij4-0001mI-Ic; Wed, 20 Sep 2017 20:23:54 +0300 Date: Wed, 20 Sep 2017 17:24:00 -0000 From: Petr Ovtchenkov To: Andreas Schwab Cc: binutils@sourceware.org, Joel Brobecker , Matthias Klose , gdb@sourceware.org Subject: Re: meaning of "Automatic date update in version.in" commits Message-ID: <20170920202354.3c863857@void-ptr.info> In-Reply-To: <87zi9p2vma.fsf@linux-m68k.org> References: <20170920173622.28500ccf@void-ptr.info> <87zi9p2vma.fsf@linux-m68k.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00055.txt.bz2 On Wed, 20 Sep 2017 18:16:45 +0200 Andreas Schwab wrote: > On Sep 20 2017, Petr Ovtchenkov wrote: > > > What is the meaning of "Automatic date update in version.in" commits? > > I mean commits like f625a739e5. > > It is used to name the shared libbfd and libopcodes, since there is no > stable ABI. > > > This commits litter commits tree and create problems for > > deterministic, bit-identical and/or verifiable builds. > > Why is that a problem? The version is fixed for a particular source > snapshot. > It's looks as a problem indeed: - garbage in commits - disorientation, when date present in SONAME 0x000000000000000e (SONAME) Library soname: [libbfd-2.29.0.20170729.so] You see: git show 3110f4be18a2 commit 3110f4be18a2f3b9fcd9663ed1dd141bbd6ed14f Author: GDB Administrator Date: Wed Sep 20 00:01:01 2017 +0000 Automatic date update in version.in diff --git a/bfd/version.h b/bfd/version.h index 3405e42..955269f 100644 --- a/bfd/version.h +++ b/bfd/version.h @@ -1,4 +1,4 @@ -#define BFD_VERSION_DATE 20170919 +#define BFD_VERSION_DATE 20170920 #define BFD_VERSION @bfd_version@ #define BFD_VERSION_STRING @bfd_version_package@ @bfd_version_string@ #define REPORT_BUGS_TO @report_bugs_to@ git show f625a739 commit f625a739e567f0110b2675539b7a0e5d5f67c5dc Author: GDB Administrator Date: Wed Sep 20 00:01:22 2017 +0000 Automatic date update in version.in diff --git a/bfd/version.h b/bfd/version.h index 3405e42..955269f 100644 --- a/bfd/version.h +++ b/bfd/version.h @@ -1,4 +1,4 @@ -#define BFD_VERSION_DATE 20170919 +#define BFD_VERSION_DATE 20170920 #define BFD_VERSION @bfd_version@ #define BFD_VERSION_STRING @bfd_version_package@ @bfd_version_string@ #define REPORT_BUGS_TO @report_bugs_to@ git diff 3110f4be18a2 f625a739 ... Ooops.... This approch produce ambiguity, but try to conceal it. -- - ptr