Summary: fix, make sure ssp actually works before using it
authorSebastian Freundt <hroptatyr@fresse.org>
Tue, 24 Jan 2012 23:45:43 +0000 (23:45 +0000)
committerSebastian Freundt <hroptatyr@fresse.org>
Tue, 24 Jan 2012 23:45:43 +0000 (23:45 +0000)
commitcd0349b46f73d6a7440544e703c15f61457f9079
tree6902385a183096e4c0d46d76d01f8d45affce8f2
parentf55522ab02b6205c44a41a4d4463a85a63be3f7b
Summary: fix, make sure ssp actually works before using it
Keywords: bldchn diagnostics

This changeset hopefully resolves the issue Nelson had with ssp and
-fstack-protector.  Using crystal ball technology and rune readings
it turns out that gcc single-handedly adds -lssp as soon as
-fstack-protector is specified, regardless if it works or exists.

* m4/sxe-compiler.m4 (SXE_STACK_FLAGS): check if ssp works before adding
  -fstack-protector

Signed-off-by: Sebastian Freundt <hroptatyr@fresse.org>
m4/sxe-compiler.m4