From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] ltrace: Explicit enable/disable of libunwind
Date: Fri, 9 Aug 2013 12:24:59 +0200 [thread overview]
Message-ID: <20130809122459.5e282d84@skate> (raw)
In-Reply-To: <1376041019-26688-2-git-send-email-jezz@sysmic.org>
Dear J?r?me Pouiller,
On Fri, 9 Aug 2013 11:36:57 +0200, J?r?me Pouiller wrote:
> ltrace automaticaly use libunwind if detected. So depending if libunwind was
automatically uses
> already compiled or not, ltrcae compile differently. This patch add explicit
ltrace compiles
This patch adds an
> dependency to libunwind if detected.
>
> In add, due to limitation of luclibc, ltrace cannot use libunwind with uclib. this patch explicitly compile without libunwind in this case.
Line should be wrapped and fixed from typos.
> diff --git a/package/ltrace/ltrace.mk b/package/ltrace/ltrace.mk
> index 7b8d859..4d81121 100644
> --- a/package/ltrace/ltrace.mk
> +++ b/package/ltrace/ltrace.mk
> @@ -13,4 +13,13 @@ LTRACE_CONF_OPT = --disable-werror
> LTRACE_LICENSE = GPLv2
> LTRACE_LICENSE_FILES = COPYING
>
> +LTRACE_LIBUNWIDFLAG = --without-libunwind
> +ifeq ($(BR2_PACKAGE_LIBUNWIND),y)
> + ifneq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
> + LTRACE_DEPENDENCIES = libunwind
> + LTRACE_LIBUNWIDFLAG = --with-libunwind
> + endif
> +endif
> +LTRACE_CONF_OPT = $(LTRACE_LIBUNWIDFLAG)
That's not how we typically write such things. We normally do something
like:
ifeq ($(BR2_PACKAGE_LIBUNWIND)$(BR2_TOOLCHAIN_USES_GLIBC),yy)
LTRACE_DEPENDENCIES += libunwind
LTRACE_CONF_OPT += --with-libunwind
else
LTRACE_CONF_OPT += --without-libunwind
endif
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-09 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 9:36 [Buildroot] [PATCH 0/3] Fix ltrace autobuilder failures Jérôme Pouiller
2013-08-09 9:36 ` [Buildroot] [PATCH 1/3] ltrace: Explicit enable/disable of libunwind Jérôme Pouiller
2013-08-09 10:23 ` Baruch Siach
2013-08-09 10:24 ` Thomas Petazzoni [this message]
2013-08-09 9:36 ` [Buildroot] [PATCH 2/3] ltrace: Fix a May be unitialized variable Jérôme Pouiller
2013-08-09 10:20 ` Baruch Siach
2013-08-09 10:28 ` Thomas Petazzoni
2013-08-09 9:36 ` [Buildroot] [PATCH 3/3] ltrace: Fix "strndup not declared" build failure on powerpc/uclibc Jérôme Pouiller
2013-08-09 10:24 ` Baruch Siach
2013-08-09 10:29 ` Thomas Petazzoni
2013-08-09 11:05 ` Thomas De Schampheleire
2013-08-09 20:30 ` 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=20130809122459.5e282d84@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