Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/strace: enable demangling of C++ symbol names in stack trace
Date: Sun, 20 May 2018 17:00:53 +0200	[thread overview]
Message-ID: <20180520170053.36c5759d@windsurf> (raw)
In-Reply-To: <20180225183415.8362-3-romain.naour@gmail.com>

Hello,

On Sun, 25 Feb 2018 19:34:15 +0100, Romain Naour wrote:

>  ...1-configure-allow-autoreconf-from-tarball.patch | 36 ++++++++++++++++++++++
>  ...0002-configure-fix-libiberty-header-check.patch | 33 ++++++++++++++++++++

In fact those patches are not necessary if you pass
--with-libiberty=check. In this case, it doesn't fail at the first
demangle.h check, and moves on to the next header file location.

So I've fixed that up, dropped the patches and AUTORECONF = YES, and
applied to next. Thanks!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-05-20 15:00 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
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 [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=20180520170053.36c5759d@windsurf \
    --to=thomas.petazzoni@bootlin.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