Vagrant Cascadian left as an exercise for the reader: > 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.
makes sense. > Does notcurses use __FILE__ macros anywhere (either directly in the > source code, or indirectly via some other build system)? Something along > those lines would be needed to completely fix the issue. yes, in its logging functionality. i'm currently using in debian/rules: export DEB_BUILD_MAINT_OPTIONS=hardening=+all reproducible=+fixfilepath CFLAGS += -ffile-prefix-map=$(CURDIR)=/ are you suggesting that removing this CFLAGS export ought be sufficient (thus relying entirely on reproducible=+fixfilepath)? i believe i needed that CFLAGS setting to ... make my python extension work? let me test it out and see. thanks! -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
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
