From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ltrace: Explicit enable/disable of libunwind
Date: Tue, 13 Aug 2013 10:42:40 +0200 [thread overview]
Message-ID: <20130813104240.1b3a3aa2@skate> (raw)
In-Reply-To: <1376382697-24789-1-git-send-email-jezz@sysmic.org>
Dear J?r?me Pouiller,
On Tue, 13 Aug 2013 10:31:37 +0200, J?r?me Pouiller wrote:
> ltrace automatically uses libunwind if detected. So depending if libunwind was
> already compiled or not, ltrace compiles differently. This patch adds explicit
> dependency to libunwind if detected.
>
> In add, due to limitation of uclibc, ltrace cannot use libunwind with uclibc.
> This patch explicitly compile without libunwind in this case.
>
> Resolve issues detected here:
> http://autobuild.buildroot.net/results/79dae85647526cdeddae5050db0339fbc38c9ae6
> http://autobuild.buildroot.net/results/808569f6bfac059b57eb4f1e692fbc9909e791cf
> http://autobuild.buildroot.net/results/83d0cd13d64053869708c666e2aa533202af67f7
>
> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
Argh, sorry, this was too late. In the mean time, Gustavo submitted a
similar patch, which I committed just minutes ago.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-08-13 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 8:31 [Buildroot] [PATCH v2] ltrace: Explicit enable/disable of libunwind Jérôme Pouiller
2013-08-13 8:42 ` Thomas Petazzoni [this message]
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=20130813104240.1b3a3aa2@skate \
--to=thomas.petazzoni@free-electrons.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