From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libunwind: new pacakge
Date: Wed, 26 Jun 2013 17:26:30 +0200 [thread overview]
Message-ID: <1372260390.2822.5.camel@sven> (raw)
In-Reply-To: <20130625235022.75b13738@skate>
Hi,
as we are also using libunwind with buildroot, perhaps I can add some of
our experiences with it...
Plain libunwind-1.1 won't compile on uClibc x86 as it uses setcontext().
This function is not available in uClibc (at least not in the released
versions). I have worked around this by commenting out some code in
libunwind (see attached patch), but this is probably not a good
solution.
I've also had a build failure at some point in the tests because there
is code that includes execinfo.h unconditionally.
I've attached the patches that we are using with libunwind. Perhaps they
can be useful for you.
Regards,
Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libunwind-001-disable-code-that-doesn-t-compile-with-uCLibc.patch
Type: text/x-patch
Size: 921 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130626/1a6ad7d3/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libunwind-002-tests-don-t-include-execinfo.h-unconditionally.patch
Type: text/x-patch
Size: 1192 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130626/1a6ad7d3/attachment-0001.bin>
next prev parent reply other threads:[~2013-06-26 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 21:41 [Buildroot] [PATCH] libunwind: new pacakge ANDY KENNEDY
2013-06-25 21:50 ` Thomas Petazzoni
2013-06-25 21:57 ` ANDY KENNEDY
2013-06-25 22:04 ` Thomas Petazzoni
2013-06-27 20:32 ` ANDY KENNEDY
2013-06-26 15:26 ` Sven Neumann [this message]
2013-06-25 21:59 ` Yann E. MORIN
2013-07-28 16:22 ` Thomas Petazzoni
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=1372260390.2822.5.camel@sven \
--to=s.neumann@raumfeld.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox