From: Wei Dai <wei.dai@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, thomas.monjalon@6wind.com,
david.marchand@intel.com, Wei Dai <wei.dai@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] add support of musl
Date: Fri, 10 Mar 2017 19:58:49 +0800 [thread overview]
Message-ID: <1489147132-40922-1-git-send-email-wei.dai@intel.com> (raw)
musl is an alternative LIBC to GLIBC.
It is an implementation of the userspace portion
of the standard library functionality described
in the ISO C and POSIX standards, plus common extensions.
Some DPDK customers fail to build DPDK with musl.
But so far execinfo.h is not supported by musl.
In order to build DPDK with musl, there is a need
to remove references to execinfo.h.
Currently only backtrace() and backtrace_symbols( ) from
execinfo.h are used in rte_dump_stack( ) in
lib/librte_eal/linuxapp/eal/eal_debug.c .
This rte_dump_stack( ) is only used to get the
name of fucntions in call stack for debugging.
Wei Dai (3):
examples/performance-thread: remove reference to execinfo.h
config: add support of musl
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 | 7 ++++++-
3 files changed, 7 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-10 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 11:58 Wei Dai [this message]
2017-03-10 11:58 ` [dpdk-dev] [PATCH 1/3] examples/performance-thread: remove reference to execinfo.h Wei Dai
2017-03-10 11:58 ` [dpdk-dev] [PATCH 2/3] config: add support of musl Wei Dai
2017-03-10 11:58 ` [dpdk-dev] [PATCH 3/3] eal: remove references to execinfo.h for musl Wei Dai
2017-03-10 12:40 ` Thomas Monjalon
2017-03-10 14:49 ` Jan Blunck
2017-03-13 8:10 ` Dai, Wei
2017-03-15 8:38 ` Jan Blunck
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=1489147132-40922-1-git-send-email-wei.dai@intel.com \
--to=wei.dai@intel.com \
--cc=david.marchand@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).