On Thu, Sep 2, 2010 at 1:41 AM, alexander.kanevs...@nokia.com wrote:
On 01/09/2010 15:24, ext Loïc Minier loic.min...@linaro.org wrote:
On Tue, Aug 31, 2010, Michael Hope wrote:
The solution is to add -fno-stack-protector to the libgcc build
options and rebuild the compiler. I've heard (but
I agree. It's also inappropriate for something as low level as libgcc
to have dependencies on other libraries such as libssp.
We'll propose a patch adding '-fno-stack-protector' to the gcc list
and see how it goes.
-- Michael
On Thu, Sep 2, 2010 at 9:23 AM, Mark Mitchell m...@codesourcery.com
Hi Chung-Lin. Could you please take care of this upstream? The short
story is that many distributions, including Fedora and Ubuntu, build
GCC with the stack protector turned on by default. This is both
inappropriate for and could interfere with libgcc. We'd like to
ensure the stack protector
Hi Alexander. I've looked into the problem and the linker error is
caused by a mix of stack protector options between libgcc and the C
library.
GCC includes a feature called the stack smashing protector which
detects writing past the end of a stack based object. It's quite nice
as it gives
