From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Dhole <"dhole@openmailbox.org">, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Allow embedded timestamps by C/C++ macros to be set externally
Date: Tue, 30 Jun 2015 14:48:00 -0000 [thread overview]
Message-ID: <5592AB0D.5000501@gmail.com> (raw)
In-Reply-To: <55929721.4020400@openmailbox.org>
On 30/06/15 15:18, Dhole wrote:
> A solution for toolchain packages that embed timestamps during the build
> process has been proposed for anyone interested and it consists of the
> following:
Perhaps this has been discussed and discarded before (if so I would appreciate
if you could point me to the relevant discussion), why not simply redefine
__DATE__ and __TIME__ to an appropriate string via the command-line or a dummy
include?
That probably triggers some warnings (or it may not be supported at all, I
haven't tried myself), but fixing those issues leads to a more general solution
than GCC reacting to an arbitrary variable name and changing its behaviour
quite silently.
Cheers,
Manuel.
next prev parent reply other threads:[~2015-06-30 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 13:19 Dhole
2015-06-30 14:48 ` Manuel López-Ibáñez [this message]
2015-06-30 14:49 ` Manuel López-Ibáñez
2015-06-30 15:42 ` Dhole
2015-06-30 16:32 ` Manuel López-Ibáñez
2015-07-03 14:00 ` Dhole
2015-06-30 17:41 ` Martin Sebor
2015-06-30 18:30 ` Mike Stump
2015-06-30 23:21 ` Joseph Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5592AB0D.5000501@gmail.com \
--to=lopezibanez@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).