I do see this bug in both sid and mostly-buster (I haven't tried
creating a new buster chroot). If only some people see this bug, but
who sees it is reproducible, that could be a sign of another problem
such as the package doing build-time hardware detection.
(https://sources.debian.org/src/highwayhash/0%7Egit20190222.276dd7b-1/README.md/#L24 says it provides both build-time-CPU-detection and
It appears to be the same bug as #923255 (which is "arch-specific"
because the expected symbol list was updated for amd64), implying that
if it is caused by a change in other packages, it appeared between
2018-11-26 (gcc 8.2.0-10, glibc 2.27-8, binutils 2.31.1-8) and
2019-02-24 (gcc 8.2.0-21, glibc 2.28-7, binutils 2.21.1-14).
It is one of 4 symbol mismatch bugs (in different packages) found in
this archive rebuild run: