[asterisk-users] Recompiling Ast results in a binary with differing SHA256 sums?

Tony Mountifield tony at softins.co.uk
Fri Jul 20 11:28:31 CDT 2018

In article <007401d41e7a$edc7e190$c957a4b0$@verishare.co.za>,
Stefan Viljoen <viljoens at verishare.co.za> wrote:
> Hi Guys
> If I recompile Asterisk (on a Centos 7 test box, Asterisk multiple
> times in a row, e. g. 
> make clean;configure;make menuselect;make
> I note that the asterisk binary in the /main folder in the source tree, has
> a different SHA256 hash each time I recompile Asterisk using the above
> commands.
> I do not change anything on the system or in the menuselect configs for each
> run.
> But each time the checksum for the "asterisk" binary is different.
> Why is that? Shouldn't a freshly compiled binary off the same source, with
> no changes in the Asterisk menuselect, with nothing changed on the rest of
> the system, result each time in an IDENTICAL binary, down to the last byte?
> Why am I getting a completely different "asterisk" ELF binary each time I
> recompile asterisk, according to checksum?
> Can someone shed light...

Most likely there is a text string in there somewhere indicating the date or
time of compilation.

Why don't you save the binary, recompile, then compare the first binary with
the recompiled one? At the simplest level use "cmp -l". Or maybe convert
each binary to a hexdump with "hexdump -C", and then use diff or vimdiff
to compare them.

Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org

More information about the asterisk-users mailing list