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 2/3] config: add a marco to enable backtrace or not
Date: Mon, 13 Mar 2017 16:59:27 +0800	[thread overview]
Message-ID: <1489395568-4664-3-git-send-email-wei.dai@intel.com> (raw)
In-Reply-To: <1489395568-4664-1-git-send-email-wei.dai@intel.com>

When building DPDK with musl, there is need not to generate
the MACRO named RTE_EAL_ENABLE_BACKTRACE in rte_config.h to
remove some references to execinfo.h which is not supported
by musl now.
This also applies to some other LIBC implementation which
doesn't support backtrace( ) and backtrace_symbols( ).

Got more details about musl from http://www.musl-libc.org .

Signed-off-by: Wei Dai <wei.dai@intel.com>
---
 config/common_linuxapp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config/common_linuxapp b/config/common_linuxapp
index 00ebaac..16e0064 100644
--- a/config/common_linuxapp
+++ b/config/common_linuxapp
@@ -37,6 +37,7 @@ CONFIG_RTE_EXEC_ENV_LINUXAPP=y
 
 CONFIG_RTE_EAL_IGB_UIO=y
 CONFIG_RTE_EAL_VFIO=y
+CONFIG_RTE_EAL_ENABLE_BACKTRACE=y
 CONFIG_RTE_KNI_KMOD=y
 CONFIG_RTE_LIBRTE_KNI=y
 CONFIG_RTE_LIBRTE_VHOST=y
-- 
2.7.4

  parent 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 [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 ` Wei Dai [this message]
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-3-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.