Re: Reproducible gcc builds, gfortran, and -grecord-gcc-switches

2012-08-16 Thread Michael Matz
Hi, On Thu, 16 Aug 2012, Simon Baldwin wrote: > Thanks for the note. > > To make things more concrete I've appended a prototype patch below. I > don't know if any other languages are affected, but if they are this > patch should extend reasonably well to cover those also. Does anyone > have

Re: Reproducible gcc builds, gfortran, and -grecord-gcc-switches

2012-08-16 Thread Simon Baldwin
On 16 August 2012 09:38, Gerald Pfeifer wrote: > > On Wed, 15 Aug 2012, Simon Baldwin wrote: > > This creates a problem for build and packaging systems that are > > fanatical about binary reproducibility and checksums. Temporary file > > names differ on each compilation, so that two different bui

Re: Reproducible gcc builds, gfortran, and -grecord-gcc-switches

2012-08-16 Thread Gerald Pfeifer
On Wed, 15 Aug 2012, Simon Baldwin wrote: > This creates a problem for build and packaging systems that are > fanatical about binary reproducibility and checksums. Temporary file > names differ on each compilation, so that two different builds of > libgfortran.a, and by extension all of gcc, will

Reproducible gcc builds, gfortran, and -grecord-gcc-switches

2012-08-15 Thread Simon Baldwin
The default setting of -grecord-gcc-switches recently changed from 0 to 1: 2012-04-25 Jakub Jelinek * common.opt (flag_debug_types_section): Default to 0. ... (dwarf_record_gcc_switches): Default to 1. Because of this, by default all objects in libraries built as p