Bug#974863: vboot-utils: uses uname to determine architecture

[Vagrant Cascadian]

Source: vboot-utils
Severity: normal
Tags: patch
User: reproducible-builds at lists.alioth.debian.org
Usertags: cpu
X-Debbugs-Cc: reproducible-bugs at lists.alioth.debian.org

When building for i386 and running an amd64 kernel, the Makefile uses
"uname -m" to determine the architecture, but this introduces variations
depending on the kernel used to perform the build:

  44277 	./host/arch/x86/lib/crossystem_arch.c:161	44277 	./host/arch/x86_64/lib/crossystem_arch.c:161

See also:

  https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/i386/diffoscope-results/vboot-utils.html
  https://tests.reproducible-builds.org/debian/issues/unstable/captures_build_arch_issue.html

While this is often worked around in chroots by running with a "linux32"
personality, using the running kernel is not the correct way to
determine the architecture.

The attached patch fixes this by passing the debian architecture via
debian/rules, and patching the Makefile to treat i386 as x86.

An alternate fix might be to determine the architecture from the
compiler or other userspace utility that is independent from the kernel,
which might be more appropriate to submit upstream.

Thanks for maintaining vboot-utils!

live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-debian-rules-Pass-the-Debian-architecture-as-_machna.patch
Type: text/x-diff
Size: 1981 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-bugs/attachments/20201115/1596f2b8/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/20201115/1596f2b8/attachment.sig>