Source: lighttpd Version: 1.4.73-1 User: debian-cr...@lists.debian.org Usertags: ftcbfs X-Debbugs-Cc: debian-cr...@lists.debian.org
Dear Maintainer, some compiler flags are architecture specific and should not leak when cross-building. As an example, -fcf-protection is x86-specific, and the following fails: aarch64-linux-gnu-gcc-13 -fcf-protection Similarly, -mbranch-protection=standard is aarch64-specific, and the following fails: x86_64-linux-gnu-gcc-13 -mbranch-protection=standard With the attached patch lighttpd cleanly cross-builds from source. Emanuele
diff -Nru lighttpd-1.4.73/debian/rules lighttpd-1.4.73/debian/rules --- lighttpd-1.4.73/debian/rules 2023-10-30 07:00:00.000000000 +0100 +++ lighttpd-1.4.73/debian/rules 2023-10-30 07:00:00.000000000 +0100 @@ -50,9 +50,9 @@ --with-xxhash \ --with-zstd \ $(if $(filter pkg.lighttpd.libunwind,$(DEB_BUILD_PROFILES)),--with-libunwind) \ - CFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CFLAGS)" \ - LDFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get LDFLAGS)" \ - CPPFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CPPFLAGS)" \ + CFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CFLAGS_FOR_BUILD)" \ + LDFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get LDFLAGS_FOR_BUILD)" \ + CPPFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CPPFLAGS_FOR_BUILD)" \ override_dh_install: cp NEWS debian/tmp/changelog