I finally did a reprotest build of systemd on armhf to try and figure out why it doesn't build reproducibly... but it built reproducibly...
My test did not test building with a 64-bit kernel (it was using a 32-bit kernel in both cases), whereas the tests.reproducible-builds.org infrastructure systematically tests one build with 64-bit kernel and one with a 32-bit kernel... The build done with a 32-bit kernel includes a reference to "arm_fadvise64_64", whereas the build with a 64-bit kernel does not: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/armhf/diffoscope-results/systemd.html Does fadvise (posix_fadvise?) on 64-bit not need any special handling, whereas on 32-bit needs a wrapper function of some kind? Not sure exactly where this behavior comes from(quite possibly in a dependent library and not systemd itself), but the build features should be determined from the userland (armhf) that it is built in, and not from which kernel is running. Sorry I don't have more conclusive results, but at least this suggests a direction to look into. live well, vagrant
signature.asc
Description: PGP signature
_______________________________________________ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
