Bug#775050: FTCBFS for arm64: failure to determine stack direction

2015-01-11 Thread Helmut Grohne
On Sat, Jan 10, 2015 at 07:53:51PM +0100, Helmut Grohne wrote: > I am attaching a patch that adds the cached value for arm64. From a > quick glance it seems or1k isn't covered either. Now really, thanks Christoph for asking. Helmut diff -Nru libsigsegv-2.10/debian/changelog libsigsegv-2.10/debian

Bug#775050: FTCBFS for arm64: failure to determine stack direction

2015-01-10 Thread Helmut Grohne
On Sat, Jan 10, 2015 at 11:37:09PM +, peter green wrote: > Can you confirm that FTCBFS stands for "fails to cross build from source"? I do. > However I would expect that either way the release team will consider this > something that should be dealt with post-jessie. I did not mean to imply

Bug#775050: FTCBFS for arm64: failure to determine stack direction

2015-01-10 Thread peter green
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 sou

Bug#775050: FTCBFS for arm64: failure to determine stack direction

2015-01-10 Thread Helmut Grohne
Package: src:libsigsegv Version: 2.10-4 Tags: patch User: helm...@debian.org Usertags: rebootstrap libsigsegv FTCBFS for arm64. 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 t