From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25696 invoked by alias); 30 Jun 2015 16:24:14 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 25664 invoked by uid 89); 30 Jun 2015 16:24:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wg0-f44.google.com Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 30 Jun 2015 16:24:12 +0000 Received: by wgck11 with SMTP id k11so14450600wgc.0 for ; Tue, 30 Jun 2015 09:24:09 -0700 (PDT) X-Received: by 10.194.201.71 with SMTP id jy7mr41581865wjc.93.1435681449745; Tue, 30 Jun 2015 09:24:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.188.139 with HTTP; Tue, 30 Jun 2015 09:23:30 -0700 (PDT) In-Reply-To: <5592B356.3080601@openmailbox.org> References: <55929721.4020400@openmailbox.org> <5592AB0D.5000501@gmail.com> <5592AC51.5040007@gmail.com> <5592B356.3080601@openmailbox.org> From: =?UTF-8?B?TWFudWVsIEzDs3Blei1JYsOhw7Fleg==?= Date: Tue, 30 Jun 2015 16:32:00 -0000 Message-ID: Subject: Re: [PATCH] Allow embedded timestamps by C/C++ macros to be set externally To: Dhole Cc: Gcc Patch List Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-06/txt/msg02239.txt.bz2 On 30 June 2015 at 17:18, Dhole wrote: > In the debian reproducible builds project we have considered several > options to address this issue. We considered redefining the __DATE__ and > __TIME__ defines by command line flags passed to gcc, but as you say, > that triggers warnings, which could become errors when building with > -Werror and thus may require manual intervention on many packages. Well, it would require adding -Wno-something (-Wno-reproducible? -Wno-unreproducible? or perhaps simply -freproducible? ) to some CFLAGS/CXXFLAGS. Is that too much manual intervention? (I'm asking sincerely, perhaps indeed it is). This could be a big hammer option that simply disables any warning that is not relevant for reproducible builds (the default being -Wsomething), for example avoid emitting --Wbuiltin-macro-redefined warnings in the specific cases of __TIME__ and __DATE. Just an idea, the maintainers would need to say if they would accept such an option. Cheers, Manuel.