On Sat, 06 Aug 2011 10:24:03 +0100, Andrew Haley <[email protected]> 
 wrote:
> On 08/05/2011 09:07 PM, Gordan Bobic wrote:
>> Thanks for pointing out, it does look like the same bug. So what's 
>> the
>> fix/workaround?
>>
>> On 08/05/2011 08:59 PM, Niels de Vos wrote:
>>> On 5 Aug 2011 19:15, "Gordan Bobic" <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>  >
>>>  > How does one pick the correct "ports" part of glibc for the 
>>> correct core?
>>>  >
>>>  > I tried to build the RHEL6 glibc with the F13 ports tar ball, 
>>> but the
>>>  > build eventually fails:
>>>  >
>>> 
>>> /usr/lib/gcc/armv5tel-redhat-linux-gnueabi/4.4.5/libgcc_eh.a(unwind-arm.o):
>>>  > In function `__gnu_Unwind_Backtrace':
>>>  > (.text+0x8b8): undefined reference to `__stack_chk_guard'
>>>  > collect2: ld returned 1 exit status
>>>
>>> Looks very much like the error in
>>> https://bugzilla.redhat.com/show_bug.cgi?id=726495
>
> What is it linking against?  __stack_chk_guard should be defined in
> libc.a.

 Indeed, nm /usr/lib/libc.a shows that __stack_chk_guard is indeed 
 defined there.

 How do I find out what it is trying to link against? There doesn't 
 appear to be anything too obvious on the output.

 Gordan
_______________________________________________
arm mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/arm

Reply via email to