On 5/5/2016 4:26 PM, Warren Young wrote:
On May 5, 2016, at 11:59 AM, Ken Brown wrote:
Ismail's suggestion did indeed produce deterministic builds in my setup. I
built a large project with about 150 executables, changed a few source files,
removed the build directory, rebuilt, and
On May 5, 2016, at 11:59 AM, Ken Brown wrote:
>
> Ismail's suggestion did indeed produce deterministic builds in my setup. I
> built a large project with about 150 executables, changed a few source files,
> removed the build directory, rebuilt, and found that only t
no-insert-timestamp hello.c
latte ~ > objdump -p a.exe | grep Time/Date
Time/Date Thu Jan 1 03:31:53 1970
Thank you! That's exactly what I was looking for.
Just for the record, in case anyone else finds this useful, Ismail's
suggestion did indeed produce deterministic
Greetings, Ken Brown!
> Is it possible to build an executable on Cygwin so that subsequent
> builds (with no change in source) produce identical results?
General answer is "no". It is possible to build a consistent object binary,
but executable linked from it will be different on different syste
On 5/4/2016 1:21 PM, Ismail Donmez wrote:
You can easily disable this feature:
latte ~ > gcc -Wl,--no-insert-timestamp hello.c
latte ~ > objdump -p a.exe | grep Time/Date
Time/Date Thu Jan 1 03:31:53 1970
latte ~ > gcc -Wl,--no-insert-timestamp hello.c
latte ~ > objdump -p a.exe |
Hi,
On Wed, May 4, 2016 at 4:38 PM, Ken Brown wrote:
> Is it possible to build an executable on Cygwin so that subsequent builds
> (with no change in source) produce identical results? Currently, the
> timestamp embedded in executables prevents this. (I don't know if that's
> the only obstacle.
Ken Brown writes:
> Is it possible to build an executable on Cygwin so that subsequent
> builds (with no change in source) produce identical results?
> Currently, the timestamp embedded in executables prevents this. (I
> don't know if that's the only obstacle.)
I think the basic problems and solu
On 2016-05-04 13:38, Ken Brown wrote:
> Is it possible to build an executable on Cygwin so that subsequent
> builds (with no change in source) produce identical results? Currently,
> the timestamp embedded in executables prevents this. (I don't know if
> that's the only obstacle.)
'-fno-guess
Is it possible to build an executable on Cygwin so that subsequent
builds (with no change in source) produce identical results? Currently,
the timestamp embedded in executables prevents this. (I don't know if
that's the only obstacle.)
For example:
$ cat hello.c
#include
int
main ()
{
pri
9 matches
Mail list logo
