etc/configure.ac | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix autoreconf failure
Bug-Debian: https://bugs.debian.org/758065

libexplain/ac/fcntl.h | 7 0 + 7 - 0 !
1 file changed, 7 deletions(-)

 do not special case alpha any longer
Bug-Debian: https://bugs.debian.org/661440

libexplain/buffer/file_inode_flags.c | 9 7 + 2 - 0 !
1 file changed, 7 insertions(+), 2 deletions(-)

 update inode flags for linux 4.5
 Linux 4.5 updated the list of inode flags including removing some existing
 flags. This patch fixes the resulting FTBFS by updating the flags list.

test/02/t0274a.sh | 8 4 + 4 - 0 !
1 file changed, 4 insertions(+), 4 deletions(-)

 fix test t0274a.sh on recent kernels
 As a result of fixing CVE-2015-8543, the behavior of creating a socket with an
 invalid protocol changed on recent kernels. Protocol numbers above 255 now
 return EINVAL. Fix the test by using a known illegal protocol and type
 combination which will fail with EPROTONOSUPPORT.

libexplain/ac/fcntl.h | 21 17 + 4 - 0 !
1 file changed, 17 insertions(+), 4 deletions(-)

 fix handling of o_largefile on various 64-bit arches

libexplain/buffer/enfile.c | 2 1 + 1 - 0 !
libexplain/buffer/errno/listen.c | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

 only compile sysctl code if sysctl exists
 The sysctl syscall is not present on arm64, so disable parts of the code which
 require it if it's not present.

explain/syscall/ustat.c | 13 1 + 12 - 0 !
1 file changed, 1 insertion(+), 12 deletions(-)

 do not require fully defined struct ustat
 Fixes ustat related FTBFS on adm64. Since explain_errno_ustat does not write to
 the data argument, it's pointless to try and allocate any memory for it anyway.

libexplain/buffer/access_mode.c | 6 3 + 3 - 0 !
libexplain/buffer/open_flags.c | 26 11 + 15 - 0 !
libexplain/parse_bits/print.c | 28 11 + 17 - 0 !
3 files changed, 25 insertions(+), 35 deletions(-)

 fix ftbfs on hppa - add handling of flags with multiple bits set
 On hppa the 'eventfd EINVAL' test was failing because the EFD_NONBLOCK was
 being incorrectly parsed. On hppa this flag sets two separate bits but the
 explain_parse_bits_print function does not handle this case. Fix by rewriting
 the algorithm to work on both cases. The access_modes table needed reordering
 to keep the old behavior there (this patch might change the ordering of some
 flags). Also handle a similar situation in explain_buffer_open_flags.