All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Dai <wei.dai@intel.com>
To: dev@dpdk.org
Cc: thomas.monjalon@6wind.com, john.mcnamara@intel.com,
	david.marchand@6wind.com, raymond.tan@intel.com,
	Wei Dai <wei.dai@intel.com>
Subject: [PATCH v2 0/3] add a macro to enable support of backtrace
Date: Mon, 13 Mar 2017 16:59:25 +0800	[thread overview]
Message-ID: <1489395568-4664-1-git-send-email-wei.dai@intel.com> (raw)

Some LIBC implementation like musl doesn't support backtrace( )
and backtrace_symbols declared in execinfo.h.
Currently some DPDK customers fail to build PDDK with musl.
In order to build DPDK with musl, there is a need to
reomve references toexecinfo.h.

Add a configuration parameter in config/common_linuxapp which equals to y 
by default. It also generate a macro named as RTE_EAL_ENABLE_BACKTRACE when 
this configuration paramter equals to y or no above macro when it is n.

---
changes:
v2 -- change configuration parameter name


Wei Dai (3):
  examples/performance-thread: remove reference to execinfo.h
  config: add a marco to enable backtrace or not
  eal: remove references to execinfo.h for musl

 config/common_linuxapp                           | 1 +
 examples/performance-thread/common/lthread_tls.c | 1 -
 lib/librte_eal/linuxapp/eal/eal_debug.c          | 4 ++++
 3 files changed, 5 insertions(+), 1 deletion(-)

-- 
2.7.4

             reply	other threads:[~2017-03-13  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13  8:59 Wei Dai [this message]
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   ` [PATCH v3 0/2] add a macro to disable support of backtrace Thomas Monjalon

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=1489395568-4664-1-git-send-email-wei.dai@intel.com \
    --to=wei.dai@intel.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=raymond.tan@intel.com \
    --cc=thomas.monjalon@6wind.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.