[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] libunwind, autotools, and ARM?

From: Steffen Sledz
Subject: Re: [Libunwind-devel] libunwind, autotools, and ARM?
Date: Tue, 03 Aug 2010 10:44:29 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1

Am 02.08.2010 18:32, schrieb Arun Sharma:
>>  AC_CHECK_LIB([unwind], [_Unwind_Backtrace], [], [ AC_MSG_ERROR([*** Could 
>> not find libunwind ***]) ])
> _Unwind_Backtrace could be provided by other libraries as well. I'd
> test for something specific to libunwind (eg: unw_step).

This is not a good idea. unw_step is not a symbol from the library but only a 
define. So the check definitely fails.

Also this seems not the real problem. If i'm right linking with -lunwind at the 
arm (and only there) results in some missing symbols:

configure:3615: gcc -o conftest -g -O2   conftest.c -ldbus-1  -lunwind  >&5
/usr/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../ undefined 
reference to `__aeabi_unwind_cpp_pr0'
/usr/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../ undefined 
reference to `__aeabi_unwind_cpp_pr1'

Somewhere i read that additionally linking -lgcc_s may fix the problem. But i 
do not really understand the background. Is this really necessary? Just at arm? 
How to reflect this in


PS: Another idea is to link the static libunwind.a library instead. But same 
problem here. How to reflect this in and/or

reply via email to

[Prev in Thread] Current Thread [Next in Thread]