Summary: | sys-libs/tdb injects -fstack-protector into CFLAGS based on bad test | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Gentoo's SAMBA Team <samba> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | hppa, matoro_bugzilla_gentoo, samba |
Priority: | Normal | Keywords: | PATCH |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | tdb-1.3.1-fstack-protector.patch |
Actually, 1.2 does this too. Fixed in tdb-1.2.12: https://github.com/samba-team/samba/commit/162ec83f68efc89c46630f6842700bca8f16b201 |
Created attachment 385098 [details, diff] tdb-1.3.1-fstack-protector.patch Checking compiler accepts ['-fstack-protector'] : yes Checking linker accepts ['-fstack-protector'] : yes # echo 'int maint() { :; }' | hppa2.0-unknown-linux-gnu-gcc -E -fstack-protector - 1>/dev/null <stdin>:1:0: warning: -fstack-protector not supported for this target [enabled by default] # echo $? 0 The above warning is repeated for every $CC call, which is rather annoying if harmless. Besides, tdb has no business injecting that kind of compiler flag in the first place. (waf should probably focus on not crashing 2:3 times).