Package: botan1.8
Version: 1.8.5-3
Severity: serious
Tags: patch
Justification: FTBFS

o<,

yet another FTBFS due to that --cpu thingy… I'm wondering why not using
say one of the *CPU variables? Also, the choice was made to use
DEB_BUILD_*, but I guess it probably wants to know the host cpu
(DEB_HOST_*) rather than the build cpu. That might also fix the i386
special case nicely?

e.g. on master:
| k...@master:~$ dpkg-architecture|grep CPU|grep DEB_HOST
| DEB_HOST_ARCH_CPU=i386
| DEB_HOST_GNU_CPU=i486

Oh, and the failed build logs:
https://buildd.debian.org/~luk/status/package.php?p=botan1.8&suite=unstable

The following works at least for kfreebsd-amd64's configure:
| DEB_HOST_GNU_CPU ?= $(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
| CONFIGURE_FLAGS = --cpu=$(DEB_HOST_GNU_CPU)

Mraw,
KiBi.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to