Re: Glibc 2.12 issue

On Tue, Aug 31, 2010, Michael Hope wrote:

This results in the libgcc function '_gcc_Unwind_Backtrace' being built with the stack protector and the glibc library 'libanl' without. At static link time GCC sees that the stack protector is off and skips linking against libssp, causing the missing symbol error.

The solution is to add -fno-stack-protector to the libgcc build options and rebuild the compiler. I've heard (but can't track down the link) that the ARM libgcc unwind functions must be built this way in any case.

See http://svn.debian.org/wsvn/gcccvs/branches/sid/gcc-4.5/debian/patches/gcc-de... for how Debian does this.

How can we fix this in the upstream sources? Should glibc or libgcc detect this erroneous state?