Hi, Thomas I noticed that my following patch set has been superseded. It address the compile errors when DPDK is built with musl. I know some customer products like Yocto Linux and that from Roph are using DPDK with musl and they have to manually change something to build it. Roph also referenced to use DPDK with musl in his mail titled " [dpdk-dev] Compiling DPDK 17.02 using musl instead of glibc " sent on 2017-03-14
Thanks & Best Regards -Wei > -----Original Message----- > From: Dai, Wei > Sent: Monday, March 13, 2017 4:59 PM > To: dev@dpdk.org > Cc: thomas.monja...@6wind.com; Mcnamara, John > <john.mcnam...@intel.com>; david.march...@6wind.com; Tan, Raymond > <raymond....@intel.com>; Dai, Wei <wei....@intel.com> > Subject: [PATCH v2 0/3] add a macro to enable support of backtrace > > 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
