From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 4/4] lttng-babeltrace: add debug info support
Date: Wed, 2 Nov 2016 23:10:23 +0100 [thread overview]
Message-ID: <20161102231023.392100c6@free-electrons.com> (raw)
In-Reply-To: <20161102065508.3162-5-eeppeliteloop@gmail.com>
Hello,
On Wed, 2 Nov 2016 02:55:08 -0400, Philippe Proulx wrote:
> diff --git a/package/lttng-babeltrace/0002-m4-ax_lib_elfutils.m4-add-cache-variable.patch b/package/lttng-babeltrace/0002-m4-ax_lib_elfutils.m4-add-cache-variable.patch
> new file mode 100644
> index 0000000..b592d7f
> --- /dev/null
> +++ b/package/lttng-babeltrace/0002-m4-ax_lib_elfutils.m4-add-cache-variable.patch
> @@ -0,0 +1,74 @@
> +From 697ab0905c59561562dc52cd3b925781e07814f3 Mon Sep 17 00:00:00 2001
> +From: Philippe Proulx <eeppeliteloop@gmail.com>
> +Date: Wed, 2 Nov 2016 01:40:12 -0400
> +Subject: [PATCH 1/3] m4/ax_lib_elfutils.m4: add cache variable
Please use git format-patch -N to generate the patches. I've fixed that
up manually.
> +
This patch really needed a better commit log, so I've added some
details here.
Essentially: an empty commit log for a non-trivial patch is always a
bug. And I believe this rule is not Buildroot specific.
> +if BR2_PACKAGE_LTTNG_BABELTRACE
> +
> +config BR2_PACKAGE_LTTNG_BABELTRACE_DEBUG_INFO
> + bool
> + default y
> + depends on !BR2_bfin # elfutils
> + depends on !BR2_STATIC_LIBS # elfutils
> + depends on BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC # elfutils
> + select BR2_PACKAGE_ELFUTILS
> +
> +comment "handling debug info in traces needs a glibc or uClibc toolchain w/ dynamic library"
> + depends on !BR2_bfin # elfutils
> + depends on BR2_STATIC_LIBS \
> + || !(BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC)
> +
> +endif
This stuff is really complicated, so I've instead removed the
sub-option, and simply made lttng-babeltrace.mk enable debug info
support when BR2_PACKAGE_ELFUTILS=y.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-02 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 6:55 [Buildroot] [PATCH v4 0/4] Update LTTng packages to 2.8.x and Babeltrace to 1.4.0 Philippe Proulx
2016-11-02 6:55 ` [Buildroot] [PATCH v4 1/4] lttng-tools: bump to version 2.8.2 Philippe Proulx
2016-11-02 6:55 ` [Buildroot] [PATCH v4 2/4] lttng-babeltrace: bump to version 1.4.0 Philippe Proulx
2016-11-02 6:55 ` [Buildroot] [PATCH v4 3/4] lttng-babeltrace: add host Babeltrace as host utility Philippe Proulx
2016-11-02 6:55 ` [Buildroot] [PATCH v4 4/4] lttng-babeltrace: add debug info support Philippe Proulx
2016-11-02 22:10 ` Thomas Petazzoni [this message]
2016-11-02 23:01 ` Philippe Proulx
2016-11-03 8:23 ` Thomas Petazzoni
2016-11-02 22:08 ` [Buildroot] [PATCH v4 0/4] Update LTTng packages to 2.8.x and Babeltrace to 1.4.0 Thomas Petazzoni
2016-11-02 22:15 ` Thomas Petazzoni
2016-11-02 23:05 ` Philippe Proulx
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=20161102231023.392100c6@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 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.