From: Randy MacLeod <randy.macleod@windriver.com>
To: Fathi Boudra <fathi.boudra@linaro.org>, ChenQi <Qi.Chen@windriver.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] libunwind: add aarch64 support
Date: Tue, 20 Sep 2016 10:21:33 -0400 [thread overview]
Message-ID: <d8e2a387-eae9-8436-e08e-4768785bd545@windriver.com> (raw)
In-Reply-To: <CAGNsrLDLQ0sJZyec8KwHxwuFGhMhP5mG+nFbFnR3816oD1MS-g@mail.gmail.com>
On 2016-09-20 07:57 AM, Fathi Boudra wrote:
> Hi,
>
> On 20 September 2016 at 05:12, ChenQi <Qi.Chen@windriver.com
> <mailto:Qi.Chen@windriver.com>> wrote:
>> On 09/26/2014 05:59 PM, Fathi Boudra wrote:
>>>
>>> * pass --enable-debug-frame on aarch64 architecture
>>
>>
>> Hi Fathi,
>>
>> I'm now dealing with a problem related to libunwind support on aarch64.
>> Could you please tell me why '--enable-debug-frame' is needed for aarch64?
>
> libunwind needs to be configured with --enable-debug-frame to prevent a
> linkage error.
> Note: --enable-debug-frame is automatically selected on ARM32, not on ARM64.
>
Thanks.
We dropped the configuration flag and don't see any linking/linkage
problems yet. Can you be more specific about the problems encountered?
Our goal is to make tcmalloc from gperftools work on ARM64.
../Randy
>> Best Regards,
>> Chen Qi
>
> Cheers,
> Fathi
>
>
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON,
Canada, K2K 2W5
next prev parent reply other threads:[~2016-09-20 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 9:59 [PATCH v2] libunwind: add aarch64 support Fathi Boudra
2014-09-28 7:39 ` Kang Kai
2016-09-20 2:12 ` ChenQi
2016-09-20 11:57 ` Fathi Boudra
2016-09-20 14:21 ` Randy MacLeod [this message]
2016-09-20 20:47 ` Khem Raj
2016-09-22 8:56 ` Fathi Boudra
2016-09-22 9:10 ` Fathi Boudra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8e2a387-eae9-8436-e08e-4768785bd545@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Qi.Chen@windriver.com \
--cc=fathi.boudra@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.