Hi Alex, At 2025-09-20T10:02:32+0200, Alejandro Colomar wrote: > On Fri, Sep 19, 2025 at 09:49:45PM -0500, G. Branden Robinson wrote: > > At 2025-09-11T09:29:23-0500, G. Branden Robinson wrote: > > > At 2025-09-11T10:59:19+0200, Alejandro Colomar wrote: > > > > I'm trying hard to have reproducible builds, so that I can > > > > verify that my build system produces the same exact thing as > > > > long as the tools used with it are the same (or a reasonably > > > > similar version). > > [...] > > > > Is groff(1) just random in some sense? Would it be possible to > > > > remove that randomness from groff(1)? > > > > > > I'll need to look at what data structure is being used to house > > > the list of file names that get dumped into GNU troff(1)'s output > > > for HTML devices. I suspect that feature was put in as a > > > grohtml(1) debugging aid, as there's nothing about it that > > > necessarily couples it to the HTML format. Output for any target > > > device could dump into its grout the list of input files that were > > > read during formatting. > > > > I can't account for this behavior. > > Have you been able to reproduce it at least?
I actually cannot. $ cd ~/src/GIT/man-pages $ git describe man-pages-6.15-107-gf17990c24 $ for n in $(seq 0 9); do groff -man -Thtml -Z ./man5/proc_pid_maps.5 \ > /tmp/proc_pid_maps.5.$n.grout; done $ cksum /tmp/proc_pid_maps.5.* 2817718111 12998 /tmp/proc_pid_maps.5.0.grout 2817718111 12998 /tmp/proc_pid_maps.5.1.grout 2817718111 12998 /tmp/proc_pid_maps.5.2.grout 2817718111 12998 /tmp/proc_pid_maps.5.3.grout 2817718111 12998 /tmp/proc_pid_maps.5.4.grout 2817718111 12998 /tmp/proc_pid_maps.5.5.grout 2817718111 12998 /tmp/proc_pid_maps.5.6.grout 2817718111 12998 /tmp/proc_pid_maps.5.7.grout 2817718111 12998 /tmp/proc_pid_maps.5.8.grout 2817718111 12998 /tmp/proc_pid_maps.5.9.grout Regards, Branden
signature.asc
Description: PGP signature
