@Dave consider that dpkg-buildflags is sensitive to the dpkg arch env variables. E.g.:
$ DEB_HOST_ARCH=amd64 dpkg-buildflags --get CFLAGS -g -O2 -ffile-prefix-map=/tmp=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection $ DEB_HOST_ARCH=armhf dpkg-buildflags --get CFLAGS -g -O2 -ffile-prefix-map=/tmp=. -fstack-protector-strong -Wformat -Werror=format-security $
While stripping this one flag may fix the build, ideally we would have a more general fix that uses target-appropriate flags for the cross-build.
@Dave consider that dpkg-buildflags is sensitive to the dpkg arch env variables. E.g.:
$ DEB_HOST_ARCH=amd64 dpkg-buildflags --get CFLAGS prefix- map=/tmp= . -flto=auto -ffat-lto-objects -fstack- protector- strong -fstack- clash-protectio n -Wformat -Werror= format- security -fcf-protection prefix- map=/tmp= . -fstack- protector- strong -Wformat -Werror= format- security
-g -O2 -ffile-
$ DEB_HOST_ARCH=armhf dpkg-buildflags --get CFLAGS
-g -O2 -ffile-
$
While stripping this one flag may fix the build, ideally we would have a more general fix that uses target-appropriate flags for the cross-build.