Note: not wearing any partciular hat in this message, opinions are my own.
Helmut Grohne wrote:
Package: src:libsigsegv
Version: 2.10-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
libsigsegv FTCBFS for arm64.
Can you confirm that FTCBFS stands for "fails to cross build from source"?
The configure script fails to determine the
stack direction. The general way of determining stack direction in
libsigsegv is to have a long list of cpu names to look up the stack
direction and only then fall back to doing a compile-run test. For
native builds this check makes the package work for arm64, but it cannot
be run while cross compiling.
I argue that since libsigsegv covers lots of other architectures, it
should also cover arm64 (consistency). Alternatively, one can argue that
cross builders should set sv_cv_stack_direction. If you believe that the
latter is the right way to go, please close this bug after tagging it
wont-fix.
I do not know enough about autotools cross-building to get involved in
the argument over which approach is better.
However I would expect that either way the release team will consider
this something that should be dealt with post-jessie.
I am attaching a patch that adds the cached value for arm64. From a
quick glance it seems or1k isn't covered either.
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
