Source: botan
Version: 2.6.0-3
Severity: important
User: [email protected]
Usertags: cpu-detection

Hi!

I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.

botan is one such package - its configure.py is way too prescriptive
about matching up CPU architecture versions. It doesn't cope with an
"armv8l" CPU type running a 32-bit userland, even though that's a
perfectly valid configuration for lots of machines.

botan could do with fixing upstream (maybe by simply adding "armv8l"
as an alias in src/build-data/arch/arm32.txt?), or failing that by
adding another override in the debian/rules file to specify the right
CPU target. There's already one there for armhf, so I guess adding
another one for armel to say

  $(if $(filter $(DEB_HOST_ARCH), armel),--cpu=armel)

*might* be an answer here.

For reference, the full build log is online at

  
https://www.einval.com/debian/arm/rebuild-logs/armel/FAIL/botan_2.6.0-3_armel.log

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Reply via email to