From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/strace: add missing libunwind optional dependency
Date: Sat, 31 Mar 2018 22:47:44 +0200 [thread overview]
Message-ID: <877epst1jj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LWD8d24hEY2UJAJckCYfrTsTA5pDgN7YrFBwDngU7xcxw@mail.gmail.com> (Thomas De Schampheleire's message of "Sun, 25 Feb 2018 22:58:39 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
Hi,
>>> In our local tree, I had added a config option to strace for that, but
>>> perhaps that is overkill?
>>
>> Are you saying that you have changes in your local tree on packages
>> available in upstream Buildroot, and you did not submit such
>> changes ? :-)
>>
> Haha, yes indeed :-) But you may be glad to hear that I already made a
> list of such changes that should be upstreamable, and plan to tackle
> the upstreaming after merging 2018.02!
Did you already get 2018.02 merged? ;)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-31 20:47 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
2018-02-25 21:34 ` Thomas Petazzoni
2018-02-25 21:58 ` Thomas De Schampheleire
2018-03-31 20:47 ` Peter Korsgaard [this message]
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=877epst1jj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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