From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] leaktracer: New package
Date: Sun, 24 Jul 2016 23:49:32 +0200 [thread overview]
Message-ID: <20160724234932.276586df@free-electrons.com> (raw)
In-Reply-To: <f6cb2b96-270c-d11e-d6dd-c8d4fc14d00c@gmail.com>
Hello,
On Wed, 6 Jul 2016 23:35:24 +0200, Romain Naour wrote:
> > diff --git a/package/leaktracer/Config.in b/package/leaktracer/Config.in
> > new file mode 100644
> > index 0000000..18c07a7
> > --- /dev/null
> > +++ b/package/leaktracer/Config.in
> > @@ -0,0 +1,8 @@
> > +config BR2_PACKAGE_LEAKTRACER
> > + bool "leaktracer"
>
> leaktracer must depends on !musl and !uClibc-ng since it use execinfo.h
>
> libleaktracer/include/MemoryTrace.hpp:25:22: fatal error: execinfo.h: No such
> file or directory
> #include <execinfo.h>
>
> see
> http://www.openwall.com/lists/musl/2015/04/09/3
Or alternatively (better), make sure that the Makefile does not pass
-DUSE_BACKTRACE. Indeed, it is already planned in the leaktracer source
code to support systems with <execinfo.h>. Maybe a simple patch to the
Makefile would allow passing a make variable to disable backtrace usage.
Maxime, can you look into this and respin a new version of this patch?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-24 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 22:31 [Buildroot] [PATCH] leaktracer: New package Maxime Hadjinlian
2016-07-06 21:35 ` Romain Naour
2016-07-24 21:49 ` 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=20160724234932.276586df@free-electrons.com \
--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