DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: YZ Xie <xiedeacc@gmail.com>
Cc: users@dpdk.org
Subject: Re: execinfo.h: No such file or directory when cross compile with musl-gcc
Date: Wed, 20 Apr 2022 18:20:07 -0700	[thread overview]
Message-ID: <20220420182007.73d14ee9@hermes.local> (raw)
In-Reply-To: <CAE5k7d+34hZVunu3zhXJnM6nNEnuwmtda8fHX29a=N-xZisxPA@mail.gmail.com>

On Thu, 21 Apr 2022 08:54:54 +0800
YZ Xie <xiedeacc@gmail.com> wrote:

> platform:generic
> arch:aarch64
> cpu:'armv8-a
> 
> compile error log:
> FAILED: lib/librte_eal.a.p/eal_linux_eal_debug.c.o
> aarch64-openwrt-linux-musl-gcc -Ilib/librte_eal.a.p -Ilib -I../lib -I. -I..
> -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include
> -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/arm/include
> -I../lib/eal/arm/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal
> -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics
> -Ilib/telemetry -I../lib/telemetry
> -I/root/src/software/openwrt-sdk-rockchip-armv8_gcc-11.2.0_musl.Linux-x86_64/staging_dir/target-aarch64_generic_musl/usr/include
> -I/root/src/software/openwrt-sdk-rockchip-armv8_gcc-11.2.0_musl.Linux-x86_64/staging_dir/toolchain-aarch64_generic_gcc-11.2.0_musl/usr/include
> -I/root/src/software/openwrt-sdk-rockchip-armv8_gcc-11.2.0_musl.Linux-x86_64/staging_dir/toolchain-aarch64_generic_gcc-11.2.0_musl/include/fortify
> -I/root/src/software/openwrt-sdk-rockchip-armv8_gcc-11.2.0_musl.Linux-x86_64/staging_dir/toolchain-aarch64_generic_gcc-11.2.0_musl/include
> -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
> -Wextra -include rte_config.h -Wcast-qual -Wdeprecated -Wformat
> -Wformat-nonliteral -Wformat-security -Wmissing-declarations
> -Wmissing-prototypes -Wnested-externs -Wold-style-definition
> -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings
> -Wno-address-of-packed-member -Wno-packed-not-aligned
> -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -Os
> -pipe -mcpu=generic -fno-caller-saves -fno-plt -fhonour-copts
> -Wno-error=unused-but-set-variable -Wno-error=unused-result
> -ffile-prefix-map=/root/src/software/openwrt-sdk-rockchip-armv8_gcc-11.2.0_musl.Linux-x86_64/build_dir/target-aarch64_generic_musl/dpdk-22.03=dpdk-22.03
> -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1
> -Wl,-z,now -Wl,-z,relro -fPIC -march=armv8-a+crc -moutline-atomics
> -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation
> '-DABI_VERSION="22.1"' -DRTE_LIBEAL_USE_GETENTROPY
> -DRTE_LOG_DEFAULT_LOGTYPE=lib.eal -MD -MQ
> lib/librte_eal.a.p/eal_linux_eal_debug.c.o -MF
> lib/librte_eal.a.p/eal_linux_eal_debug.c.o.d -o
> lib/librte_eal.a.p/eal_linux_eal_debug.c.o -c ../lib/eal/linux/eal_debug.c
> ../lib/eal/linux/eal_debug.c:6:10: fatal error: execinfo.h: No such file or
> directory
>     6 | #include <execinfo.h>
>       |          ^~~~~~~~~~~~

You need to disable RTE_BACKTRACE_STACK in the config.
musl is a small library and probably doesn't have backtrace_symbols()

  reply	other threads:[~2022-04-21  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  0:54 YZ Xie
2022-04-21  1:20 ` Stephen Hemminger [this message]
2022-05-20 20:50 ` Stephen Hemminger

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=20220420182007.73d14ee9@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=xiedeacc@gmail.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).