On Wed, Nov 6, 2013 at 7:37 AM, Tom Tromey tro...@redhat.com wrote:
Tobias == Tobias Burnus bur...@net-b.de writes:
Tobias + cpp_warning (pfile, CPP_W_DATE_TIME, Macro \%s\ might
prevent
Tobias + reproduce builds, NODE_NAME (node));
Tobias + cpp_warning
Ian Lance Taylor wrote:
On Wed, Nov 6, 2013 at 7:37 AM, Tom Tromey tro...@redhat.com wrote:
Tobias + cpp_warning (pfile, CPP_W_DATE_TIME, Macro \%s\ might prevent
Tobias + reproduce builds, NODE_NAME (node));
Tobias + cpp_warning (pfile, CPP_W_DATE_TIME,
On Mon, Nov 04, 2013 at 09:58:30PM +0100, Tobias Burnus wrote:
Tobias Burnus wrote:
Gerald Pfeifer wrote:
To make it easier to reproduce builds of software and entire GNU/Linux
distributions, RMS had the idea of adding a warning to GCC that warns
about the use of __DATE__ and __TIME__.
On Mon, Nov 04, 2013 at 09:58:30PM +0100, Tobias Burnus wrote:
Tobias Burnus wrote:
Gerald Pfeifer wrote:
To make it easier to reproduce builds of software and entire GNU/Linux
distributions, RMS had the idea of adding a warning to GCC that warns
about the use of __DATE__ and __TIME__.
Tobias Burnus wrote:
Gerald Pfeifer wrote:
To make it easier to reproduce builds of software and entire GNU/Linux
distributions, RMS had the idea of adding a warning to GCC that warns
about the use of __DATE__ and __TIME__.
I assume that he also likes to have a warning for __TIMESTAMP__.
I
The warning should say macro not Macro and I think reproducing not
reproduce. The c-family and libcpp changes are OK with that fixed.
--
Joseph S. Myers
jos...@codesourcery.com
Tobias Burnus wrote:
Gerald Pfeifer wrote:
To make it easier to reproduce builds of software and entire GNU/Linux
distributions, RMS had the idea of adding a warning to GCC that warns
about the use of __DATE__ and __TIME__.
I assume that he also likes to have a warning for __TIMESTAMP__.
I
The warning should say macro not Macro and I think reproducing not
reproduce. The c-family and libcpp changes are OK with that fixed.
--
Joseph S. Myers
jos...@codesourcery.com
