libcap/cap_names.header | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 hide private symbols

Hide a symbol which is clearly meant to be private. This resolves a FTBFS in
combination with the new build dependency gperf.

Closes: #793311
Closes: #869588

Bug-Debian: https://bugs.debian.org/793311
Bug-Debian: https://bugs.debian.org/869588

libcap/Makefile | 4 4 + 0 - 0 !
pam_cap/Makefile | 4 4 + 0 - 0 !
2 files changed, 8 insertions(+)

 filter out pie flags when building shared objects

Filter out -pie, -fpie, and -fPIE when building the shared library and the PAM
module. This way, hardening=+all can be used unconditionally in debian/rules.

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 skip git if not installed

This is only used during the clean stage. For a typical Debian package build,
git will not be installed.

Bug-Debian: https://bugs.debian.org/1046986

libcap/execable.h | 11 11 + 0 - 0 !
1 file changed, 11 insertions(+)

 glibc needs a constant to be defined for puts() to work.

See https://bugzilla.kernel.org/show_bug.cgi?id=219880

Signed-off-by: Andrew G. Morgan <morgan@kernel.org>

psx/psx_calls.c | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 add support for some less mainstream architectures.

These (__alpha__, __hppa__, __sh__) don't have the SA_RESTORER
complication, so hopefully can "just work". I'm relying on Debian's
build servers to confirm.

See: https://bugzilla.kernel.org/show_bug.cgi?id=219915

Signed-off-by: Andrew G. Morgan <morgan@kernel.org>

psx/psx_calls.c | 19 11 + 8 - 0 !
1 file changed, 11 insertions(+), 8 deletions(-)

 extend support further to __m68k__ and possibly __sparc__.

This may include a needed fix for __sh__ too.

I don't have any test machines for this, so this code change
is untested, and based solely on reading kernel etc. sources.

Signed-off-by: Andrew G. Morgan <morgan@kernel.org>

psx/psx_calls.c | 37 29 + 8 - 0 !
1 file changed, 29 insertions(+), 8 deletions(-)

 be more systematic using the kernel signal handler apis.

Each architecture seems to have its own nuance. Found a way
to get the kernel header compilation to confirm what sigaction