This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Allow embedded timestamps by C/C++ macros to be set externally
- From: Mike Stump <mikestump at comcast dot net>
- To: Martin Sebor <msebor at gmail dot com>
- Cc: Dhole <dhole at openmailbox dot org>, gcc-patches at gcc dot gnu dot org, Manuel López-Ibáñez <lopezibanez at gmail dot com>
- Date: Tue, 30 Jun 2015 11:07:24 -0700
- Subject: Re: [PATCH] Allow embedded timestamps by C/C++ macros to be set externally
- Authentication-results: sourceware.org; auth=none
- References: <55929721 dot 4020400 at openmailbox dot org> <5592AB0D dot 5000501 at gmail dot com> <5592AC51 dot 5040007 at gmail dot com> <5592B356 dot 3080601 at openmailbox dot org> <5592D42C dot 2080503 at gmail dot com>
On Jun 30, 2015, at 10:38 AM, Martin Sebor <msebor@gmail.com> 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.
>
> Would replacing the localtime function with one of your own
> in a DSO and preloading the DSO when invoking GCC be a viable
> solution?
No please. Not all systems have shared libraries, preloading and so on. Indeed, I like building on my target system using the simulator, no shared libraries around.