Reproducible Buildsappview XRPC

libfftw3-mpi-dev 3.3.10-2+b1 debian

libfftw3-mpi-dev_3.3.10-2+b1_armel.debsha256 0aeb234cfae8e0926df3433dbfb8c55bcbeec8c66279a100517465199fd82753

unverified

0 of 3 required independent builders reproduced this artifact bit for bit, each with an attestation signed by a key its DID document declares.

one more verified builderone more verified builderone more verified builder
threshold
123
distinct builders; the first-party build never counts

Claims by builder

1 record, newest first
Builder
reproduce.debian.net (armel) via bridgedid:web:armel.reproduce.debian.net.rbld.dev
Outcomemismatch no rebuilt artifact
finished 2026-02-28 10:04 UTC
Attestationnonerebuilders attest only byte-identical results
at://did:web:armel.reproduce.debian.net.rbld.dev/org.reproducible-builds.rebuild/0aeb234cfae8e0926df3433dbfb8c55bcbeec8c66279a100517465199fd82753

reproducible-notes

source package fftw3
noted at version 3.3.8-2
records_build_flags
Records $CFLAGS, which vary intentionally due to the «-fdebug-prefix-map=${BUILDPATH}=.», «-ffile-prefix-map=${BUILDPATH}=.» or «-fmacro-prefix-map=${BUILDPATH}=.» flags. . We have a patch pending to GCC to fix this issue centrally: . https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00182.html . Though the patch is currently unlikely to be merged. If/when this is accepted, this issue should be fixed for all packages and you should not need to fix it specifically in your package. . There is also a work-in-progress patch to dpkg that could address this issue: . https://bugs.debian.org/985553 . For more background information see: . • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160822/006788.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160905/006984.html • https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20160912/007076.html