< dongcarl> Does gitian use a particular gcc version?
< CubicEarths> Is anyone else getting spammed with arowers joined and leaves?
< luke-jr> yes
< luke-jr> I suppose we should ban-redirect him to ##fix-your-connection or whatever the channel is
< midnightmagic> I'm not +o in here; I can't help. Sorry.
< * kallewoof> filters out join/leave msgs
< dongcarl> Hi all, I'm working on integrating landley's mkroot into gitian... Here's a link: https://github.com/landley/mkroot I'm wondering if gitian builds bitcoin with a particular version of gcc, and if I need to build it with a particular version of gcc for the binary to be reproducible, as I'm seeing that the different suites we support for ubuntu has differing default gcc versions
< * dongcarl> waits patiently
< sipa> dongcarl: different gcc versions will inevitably produce different binaries
< dongcarl> sipa: that's what I thought, so how does gitian handle that? Do we build a particular version of gcc inside the container/vm that does that actual build of bitcoind?
< dongcarl> Asking because "I'm seeing that the different suites we support for ubuntu has differing default gcc versions"
< sipa> dongcarl: gitian's environment is completely determined by the descriptors
< dongcarl> sipa: I see what you're saying, so it'll always be trusty and "gcc-4.8-aarch64-linux-gnu"
< sipa> dongcarl: not always; it's specific to the version being built
< dongcarl> sipa: you mean whatever's specified in bitcoin/contrib/gitian-descriptors/gitian-linux.yml for the version built?
< sipa> yes
< dongcarl> Ah yes, makes sense. So in this way, if the "gcc-4.8-aarch64-linux-gnu" package was updated in the canonical repos, and some developers did an upgrade in gitian and some didn't, we would get differing binaries?
< * dongcarl> trying to validate my assumptions
< achow101> dongcarl: no, all gitian builds are done in newly created trusty environments (as in gitian creates those) where everything is then installed and upgraded. so for a particular version, unless the package updates in the middle of the build process, everyone should be using the same version packages
< dongcarl> achow101: how about in this timeline: 1. person x gitian-builds 0.17, 2. gcc package updates, 3. person y gitian-builds 0.17
< achow101> dongcarl: then we may see differing resulting hashes. This is easy to spot since all packages, their version numbers, and their hashes are recorded in the gitian output files.
< achow101> so then person x just rebuilds
< dongcarl> achow101: haha yeah that's what I thought :-)
< satwo> Hello all. My Travis CI build failed on something totally unrelated to the changed file, though it had succeeded twice previously (the only changes being to documentation). Can anyone advise me on how to proceed? Here's the PR: https://github.com/bitcoin/bitcoin/pull/13589
< satwo> Nevermind, all figured out.