From: Thomas Monjalon <thomas@monjalon.net>
To: Wei Dai <wei.dai@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 0/2] add a macro to disable support of backtrace
Date: Fri, 05 May 2017 15:21:55 +0200 [thread overview]
Message-ID: <2003676.404iG6dgLJ@xps> (raw)
In-Reply-To: <20170505131827.25599-1-thomas@monjalon.net>
05/05/2017 15:18, Thomas Monjalon:
> Some LIBC implementation like musl doesn't support backtrace()
> and backtrace_symbols() declared in execinfo.h.
> Currently some DPDK customers fail to build DPDK with musl.
> In order to build DPDK with musl, there is a need to
> remove references to execinfo.h.
>
> Add a configuration parameter which defaults to y.
>
> v3:
> - rename option
> - apply to BSD
> - squash patches
>
> Wei Dai (2):
> examples/performance-thread: remove useless include
> config: make backtrace optional
I prefer this version ;)
Applied, thanks
prev parent reply other threads:[~2017-05-05 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 8:59 [PATCH v2 0/3] add a macro to enable support of backtrace Wei Dai
2017-03-13 8:59 ` [PATCH v2 1/3] examples/performance-thread: remove reference to execinfo.h Wei Dai
2017-03-15 8:39 ` Jan Blunck
2017-03-13 8:59 ` [PATCH v2 2/3] config: add a marco to enable backtrace or not Wei Dai
2017-03-13 8:59 ` [PATCH v2 3/3] eal: remove references to execinfo.h for musl Wei Dai
2017-05-05 1:30 ` [PATCH v2 0/3] add a macro to enable support of backtrace Dai, Wei
2017-05-05 13:18 ` [PATCH v3 0/2] add a macro to disable " Thomas Monjalon
2017-05-05 13:18 ` [PATCH v3 1/2] examples/performance-thread: remove useless include Thomas Monjalon
2017-05-05 13:18 ` [PATCH v3 2/2] config: make backtrace optional Thomas Monjalon
2017-05-05 13:21 ` Thomas Monjalon [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=2003676.404iG6dgLJ@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=wei.dai@intel.com \
/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.