[Reproducible-commits] [reproducible-builds-howto] 01/02: Mention tricks for removing randomness from GCC output

[Jérémy Bobbio]

This is an automated email from the git hooks/post-receive script.

lunar pushed a commit to branch master
in repository reproducible-builds-howto.

commit c46beb30171dbfec370611b983307ac979033c9b
Author: Jérémy Bobbio <lunar at debian.org>
Date:   Wed Aug 5 14:11:30 2015 +0200

    Mention tricks for removing randomness from GCC output
---
 reproducible-builds-howto.mdwn | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/reproducible-builds-howto.mdwn b/reproducible-builds-howto.mdwn
index c3c4ba1..e5e65e5 100644
--- a/reproducible-builds-howto.mdwn
+++ b/reproducible-builds-howto.mdwn
@@ -121,6 +121,8 @@ Avoid true randomness
 
 Don't ship any data created using properly random sources. Avoid using random data if possible. If not, use a known value as the PRNG seed. For example, extract a value using a hash of some file content, a changelog or the version control system.
 
+When using GCC, you might one to specify `-frandom-seed` if you use feature like Link-Time Optimization. Intermediate files might be created using temporary file names which will be written in debug symbols. Using `-save-temps` will make these names deterministic.
+
 Define environment variables affecting outputs
 ----------------------------------------------
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-builds-howto.git