On Sun, Sep 17, 2017 at 04:33:49PM +0100, Thomas Pircher wrote: > > > hello, I find this approach a little bit too invasive > > > > > > -cxxflags="-Wall -W -pedantic -g -O2 > > > -fdebug-prefix-map=/build/libcgicc-GEfIf8/libcgicc-3.2.19=. > > > -fstack-protector-strong -Wformat -Werror=format-security" > > > +cxxflags="-Wall -W -pedantic -g -O2 > > > -fdebug-prefix-map=/build/libcgicc-pUjh6F/libcgicc-3.2.19=. > > > -fstack-protector-strong -Wformat -Werror=format-security" > > > > What's that? Have you diffed the build logs instread of the source > > packages? > > This is the diff of /usr/bin/cgicc-config between packages from different > architectures Ah. > (or possibly between two different builds?). Yes, packages recording CFLAGS are also not reproducible. See https://tests.reproducible-builds.org/debian/issues/unstable/records_build_flags_issue.html Links mentioned there may be useful to you too. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature