Vagrant Cascadian: > On 2017-08-16, Ximin Luo wrote: >> It looks like the GCC reviewer that looked at my patch this time >> around, really doesn't like environment variables. They seem to be >> happy to support the variable (including the syntax) as a command-line >> flag however. > >> The original patch fixed ~1800 packages, which were unreproducible due >> to a combination of (a) __FILE__, (b) CFLAGS et al being embedded into >> the output, and (c) packages/upstreams not honoring CFLAGS in the >> first place, and (d) possibly other reasons. > ... >> For these reasons, I have the following proposal, as a work around for the >> time being: >> >> 1. Patch GCC to support BUILD_PATH_PREFIX_MAP as a command-line flag. this >> will at least fix packages affected by (a). > > What about a compromise, patching GCC to support a commandline flag > "--respect-build-path-prefix-map-variable" that tells it to respect the > BUILD_PATH_PREFIX_MAP as an environment variable? > > The commandline flag could essentially be a boolean, and would fix (a) > as well as (b). > > Or maybe GCC is just fundamentally opposed to environment variables at > all? > > > This is perhaps a correlary to the additional variable added to some of > the latex toolchain that basically said "really, use SOURCE_DATE_EPOCH > for the current time please, please, really" >
Thanks for the suggestion. I think it's unlikely but I'll try it and if it doesn't work, do what I said originally. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git _______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds