All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/strace: add missing libunwind optional dependency
Date: Sun, 25 Feb 2018 21:50:34 +0100	[thread overview]
Message-ID: <d5803d2e-773e-10ce-71b0-e5ca69671cf8@gmail.com> (raw)
In-Reply-To: <CAAXf6LXnevwOqgTb7yV5AraDkHsauEfhJNoQr8rNgWFLQKp15Q@mail.gmail.com>

Hi Thomas,

Le 25/02/2018 ? 21:28, Thomas De Schampheleire a ?crit?:
> Hi,
> 
> 2018-02-25 19:34 GMT+01:00 Romain Naour <romain.naour@gmail.com>:
>> This improve the reproducible build.
>>
>> Signed-off-by: Romain Naour <romain.naour@gmail.com>
>> ---
>>  package/strace/strace.mk | 7 +++++++
>>  1 file changed, 7 insertions(+)
>>
>> diff --git a/package/strace/strace.mk b/package/strace/strace.mk
>> index e292c60f2a..9c1fab3871 100644
>> --- a/package/strace/strace.mk
>> +++ b/package/strace/strace.mk
>> @@ -10,6 +10,13 @@ STRACE_SITE = https://github.com/strace/strace/releases/download/v$(STRACE_VERSI
>>  STRACE_LICENSE = BSD-3-Clause
>>  STRACE_LICENSE_FILES = COPYING
>>
>> +ifeq ($(BR2_PACKAGE_LIBUNWIND),y)
>> +STRACE_DEPENDENCIES += libunwind
>> +STRACE_CONF_OPTS += --with-libunwind
>> +else
>> +STRACE_CONF_OPTS += --without-libunwind
>> +endif
>> +
> 
> As far as I know, the main (only?) reason for a libunwind dependency
> is to support 'strace -k' to get callstack info. Perhaps it would be
> useful to update the Config.in file to hint about this, i.e. that
> users should enable libunwind manually if they want 'strace -k'
> support.

Ok, why not.

> 
> In our local tree, I had added a config option to strace for that, but
> perhaps that is overkill?

Most packages optional dependencies are handled like this, otherwise we have to
maintain one config option for each optional dependencies.

Best regards,
Romain

> 
> /Thomas
> 

  reply	other threads:[~2018-02-25 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 18:34 [Buildroot] [PATCH 1/3] package/strace: bump to 4.21 Romain Naour
2018-02-25 18:34 ` [Buildroot] [PATCH 2/3] package/strace: add missing libunwind optional dependency Romain Naour
2018-02-25 20:28   ` Thomas De Schampheleire
2018-02-25 20:50     ` Romain Naour [this message]
2018-02-25 21:34     ` Thomas Petazzoni
2018-02-25 21:58       ` Thomas De Schampheleire
2018-03-31 20:47         ` Peter Korsgaard
2018-04-01  8:04           ` Thomas De Schampheleire
2018-04-06 21:38   ` Thomas Petazzoni
2018-02-25 18:34 ` [Buildroot] [PATCH 3/3] package/strace: enable demangling of C++ symbol names in stack trace Romain Naour
2018-05-20 15:00   ` 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=d5803d2e-773e-10ce-71b0-e5ca69671cf8@gmail.com \
    --to=romain.naour@gmail.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.