There is absolutely no reason, why in the ebuild is filtered: filter-flags -fstack-protector Please, remove filter-flags.
@hardened: feel free to fix, falls into your category.
I just tested this removing filter-flags -fstack-protector from the ebuilds and encountered no problems on hardened x86 and amd64 and non-hardened x86 and amd64. The flag was originally filtered to address bug 37421 which was triggered when compiling a 2.4 kernel and lm_sensors with gcc-3.3.2 with/without -fstack-protector set (thanks kallamej). This is no longer an issue on current profiles.
(In reply to comment #2) > I just tested this removing filter-flags -fstack-protector from the ebuilds and > encountered no problems on hardened x86 and amd64 and non-hardened x86 and > amd64. > > The flag was originally filtered to address bug 37421 which was triggered when > compiling a 2.4 kernel and lm_sensors with gcc-3.3.2 with/without > -fstack-protector set (thanks kallamej). This is no longer an issue on current > profiles. > Tested lm_sensors without filter flag for 2.0.7 (many months) and 3.x (lately) on x86, no problems.
fixed for 3.1.2 in cvs. thanks for the report, the research and the testing.