RE: Please review the draft for December's report
> Please review the draft for December's Reproducible Builds report: Minor mistake in regards to mescc-tools-seed We were informing you that we completed the AArch64 bootstrap to the same level as the previous knight (on bare metal), x86 and AMD64 bootstraps. Thus we have 4 independent bootstraps on 4 different architectures able to reproduce each other. And that we bootstrapped a Haskell compiler from hex0 -Jeremiah ___ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
Re: Please review the draft for December's report
Hi Jeremiah, > We were informing you that we completed the AArch64 bootstrap to the > same level as the previous knight (on bare metal), x86 and AMD64 > bootstraps. [..] Thanks for reading over the draft; suggestions/corrections/ideas are, of course, really important to make them effective. Could you suggest an alternative wording for that section in the report? Unfortunately, I don't think I can copy-paste the text you sent, as it is just slightly too technical as it stands. Best wishes, -- o ⬋ ⬊ Chris Lamb o o reproducible-builds.org 💠 ⬊ ⬋ o ___ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
Re: symbol sizes changing
Vagrant Cascadian wrote: > In unstable and experimental we do test build paths, but also pass > DEB_BUILD_OPTIONS=reproducible=+fixfilepath, which passes the > -ffile-prefix-map=BUILDPATH=. argument, stripping the build path, but > sometimes leaves traces; the length of the build path is different > (e.g. /1/2/3 vs. /1/2/3/4), so it leaves a different amount of > padded/empty space. As a slight aside, the build path varies between the two builds is currently: /build/1st/notcurses-2.1.3+dfsg.1/ /build/2/notcurses-2.1.3+dfsg.1/2nd/ … which is actually 2 bytes difference, not 4. Still, it may be referenced twice (making 4…), and padding/alignment is a thing on most architectures. (I point this out in case others are confused about a 2-byte difference offset elsewhere in the future, rather than suggesting it is the cause in this specific instance.) Best wishes, -- o ⬋ ⬊ Chris Lamb o o reproducible-builds.org 💠 ⬊ ⬋ o ___ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
RE: Please review the draft for December's report
> Could you suggest an alternative wording for that section in the report? > Unfortunately, I don't think I can copy-> paste the text you sent, as it is > just slightly too technical as it stands. Then this https://www.freelists.org/post/bootstrappable/wipfullsourcebootstrap-from-a-357byte-hex0-to-hello Would be a just a touch too technical. -Jeremiah ___ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
