On Sat, 2024-06-29 at 17:29:49 +0200, Guillem Jover wrote:
There's another regression that I found on various BSDs, where they
already have GNU make 4.4.1, where the buildtools test fails for the
AR and AR_FOR_BUILD checks, and I've not managed to track down yet
what the problem is (and whether this is an intentional behavior
change from its NEWS entry), but this needs to be fixed before a release because Debian will eventually hit that, and other systems with a new
GNU make will also fail. If you could have a look that would be appreciated, otherwise I'll try during the weekend.
I've tracked this down. The problem was that on the BSDs the dpkg
build system sets CC as the value detected at configure time, which is
cc, and for which there was no mocked binary, so the test code ended
up running as if it was cross-building, which cause the value to not
inherit from AR. I'll be adding a mock for cc, but that will not catch
CC being set to clang or another program, so this needs to be dynamic,
and so for now I'll explicitly override AR_FOR_BUILD to avoid the cross-compilation check.
(I'm also going to add some CI runs for the BSDs to avoid regressions,
but probably on a branch for github.)
There's another regression that I found on various BSDs, where they
already have GNU make 4.4.1, where the buildtools test fails for the
AR and AR_FOR_BUILD checks, and I've not managed to track down yet
what the problem is (and whether this is an intentional behavior
change from its NEWS entry), but this needs to be fixed before a release because Debian will eventually hit that, and other systems with a new
GNU make will also fail. If you could have a look that would be
appreciated, otherwise I'll try during the weekend.
You have not applied
0001-scripts-mk-stop-hard-coding-dpkg_datadir.patch
probably because you prefer the related parts in
f1175056 (build: Rework subst handling for built or installed artifacts).
Ironically, f1175056 seems to introduce the exact kind of human error
that dynamic generation would prevent. 0001-build-spare-an-unneeded-subst-handling-in-pkg-info.m.patch
diff --git a/scripts/mk/Makefile.am b/scripts/mk/Makefile.am
index be6076b2c..5f086ef49 100644
--- a/scripts/mk/Makefile.am
+++ b/scripts/mk/Makefile.am
@@ -18,5 +18,4 @@ include $(top_srcdir)/build-aux/subst.am
install-data-hook:
$(subst_make_file) $(DESTDIR)$(pkgdatadir)/default.mk
$(subst_make_file) $(DESTDIR)$(pkgdatadir)/buildtools.mk
- $(subst_make_file) $(DESTDIR)$(pkgdatadir)/pkg-info.mk
$(subst_make_file) $(DESTDIR)$(pkgdatadir)/vendor.mk
to avoid changing all pathname concatenation I changed dpkg_datadir to «$(patsubst %/,%,$(dir $(lastword $(MAKEFILE_LIST))))».then I did suggest $(patsubst %/current.mk/,%,$(lastword $(MAKEFILE_LIST))),
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 145:41:52 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,685 |