libc_cv_ssp=no required to bootstrap a cross compiler

[Christer Solskogen]

With the GCC-soon-to-be 4.8 (alias gcc-trunk) and the master branch of 
glibc I'm able to create a cross compiler without to many hacks.

binutils->static gcc->glibc->gcc works. Almost.
glibc bails out with n function `getanswer':
gethnamaddr.c:(.text+0x8b8): undefined reference to `__stack_chk_guard' 
- but with a hidden configure option ( libc_cv_ssp=no ) I am able to 
build it. I've tried with sparc,powerpc, i686 and x86_64 targets.

But is this a problem? The 'libc_cv_ssp=no' part I mean?

-- 
chs