Bug#991020: gcc-mingw-w64: embeds path to sed which differs with usrmerge

[Vagrant Cascadian]

Source: gcc-mingw-w64
Severity: normal
Tags: patch
User: reproducible-builds at lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-bugs at lists.alioth.debian.org

The path to sed is embedded in various binaries, which differs on a
usrmerge vs. non-usrmerge system.

  https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/diffoscope-results/gcc-mingw-w64.html

  ./usr/lib/gcc/i686-w64-mingw32/10-posix/install-tools/fixincl

  /bin/sed
  vs.
  /usr/bin/sed

Patch attached which passes the SED variable to configure to use the
non-usrmerge location, as usrmerge installations typically have
compatibility symlinks, but not vice-versa.


This should make gcc-mingw-w64 reproducible in the testing suite on
tests.reproducible-builds.org, but does not resolve all tested
variations (e.g. build paths) in the unstable and experimental suites.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-debian-rules-Pass-explicit-path-for-sed.patch
Type: text/x-diff
Size: 925 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-bugs/attachments/20210712/9bb38554/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-bugs/attachments/20210712/9bb38554/attachment.sig>