Package: debhelper
Version: 13.24.2
Severity: wishlist

In https://bugs.debian.org/1103589, I noticed that the upstream 
CMakeLists.txt was misdetecting the intended host architecture as arm64 
due to `CMAKE_SYSTEM_PROCESSOR MATCHES 
"^(aarch64|arm64|armv[89].?|ARM64)$"`.  debhelper's cmake buildsystem 
sets CMAKE_SYSTEM_PROCESSOR when cross-compiling to armhf, but when not 
cross-compiling it allows cmake to use its default.  According to 
https://cmake.org/cmake/help/latest/variable/CMAKE_SYSTEM_PROCESSOR.html 
that falls back to CMAKE_HOST_SYSTEM_PROCESSOR, which is just the output 
of `uname -m` when building on Linux.

For CMAKE_SYSTEM_NAME it doesn't matter since the autodetection is 
pretty likely to be correct, but it's fairly well-known that `uname -m` 
is an inappropriate thing to use when configuring package builds.  
Should debhelper perhaps pass -DCMAKE_SYSTEM_PROCESSOR also in the 
non-cross-compiling case?

Thanks,

-- 
Colin Watson (he/him)                              [[email protected]]

-- System Information:
Debian Release: 13.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.38+deb13-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debhelper depends on:
ii  autotools-dev            20240727.1
ii  dh-autoreconf            20
ii  dh-strip-nondeterminism  1.14.1-2
ii  dpkg                     1.22.21
ii  dpkg-dev                 1.22.21
ii  dwz                      0.15-1+b1
ii  file                     1:5.46-5
ii  libdebhelper-perl        13.24.2
ii  libdpkg-perl             1.22.21
ii  man-db                   2.13.1-1
ii  perl                     5.40.1-6
ii  po-debconf               1.0.21+nmu1

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.202503

-- no debconf information

Reply via email to