Maybe you have put a global -fstack-protector or -fstack-protector-all in your CFLAGS when compiling gcc, omit this since is not needed, just use the specs for this package. If you did this you will find (too) that glibc doesn't compile at all with -fstack-protector-all. In any case it could be a bug in gcc, try to update it.
2008/10/26 Magnus Granberg <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] skrev: >> On 25 Oct 2008 at 21:44, Jan Klod wrote: >> >> >>> Hello. >>> >>> I was trying to make a switch form normal, freshly installed gentoo to >>> hardened like described in PaX quickstart. >>> http://www.gentoo.org/proj/en/hardened/pax-quickstart.xml Though, that >>> guide is missing to inform about when should I boot hardened-sources. >>> Not sure if after "emerge binutils gcc virtual/libc" or "emerge -e >>> world", but I got this error, which persists: >>> >>> ============================================================================ >>> *** stack smashing detected ***: cc1 - terminated >>> cc1: stack smashing attack in function ix86_split_to_parts - terminated >>> >> >> i don't know if you're supposed to use ssp on gcc itself, but apparently it >> caught some bug, whether that's some miscompilation or a real bug in gcc, i >> can't tell from this, but it's worth a look. if you just want to finish your >> install, you should recompile gcc itself without using ssp during compilation >> (that can be tricky, i don't know where the specs file comes from in that >> case). >> >> >> > What is your emerge --info? > >
