[Top][All Lists]

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

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

From: Arun Sharma
Subject: Re: [Libunwind-devel] libunwind, autotools, and ARM?
Date: Wed, 4 Aug 2010 15:20:34 -0700

On Tue, Aug 3, 2010 at 1:44 AM, Steffen Sledz <address@hidden> wrote:
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.

The problem is: if you configure libunwind with -- enable_cxx_exceptions=no (which is the default on x86, arm, mips), you'll not have these symbols defined.

True - unw_step gets rewritten as _UL${plat}_step (see tests/ - but why should it be a problem for writing an autoconf macro as long as you're including the right header file with #define unw_step ...?


reply via email to

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