From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 222] When setting CONFIG_RTE_LIBRTE_PDUMP=n, build fails with "undefined reference to `test_pdump'"
Date: Sat, 09 Mar 2019 16:24:50 +0000 [thread overview]
Message-ID: <bug-222-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=222
Bug ID: 222
Summary: When setting CONFIG_RTE_LIBRTE_PDUMP=n, build fails
with "undefined reference to `test_pdump'"
Product: DPDK
Version: 19.02
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: ramirose@gmail.com
Target Milestone: ---
Running the following steps:
Cloning DPDK tree (git clone http://dpdk.org/git/dpdk)
make config T=x86_64-native-linuxapp-gcc
setting CONFIG_RTE_LIBRTE_PDUMP=n in build/.config
running "make"
...
...
CC test_ipsec.o
LD test
/usr/bin/ld: test.o: in function `main':
test.c:(.text.startup+0x91): undefined reference to `test_pdump'
/usr/bin/ld: test_eal_flags.o: in function `process_dup.constprop.7':
test_eal_flags.c:(.text+0x4a4): undefined reference to `flag_for_send_pkts'
/usr/bin/ld: test_eal_flags.c:(.text+0x4b3): undefined reference to `send_pkts'
collect2: error: ld returned 1 exit status
make[3]: *** [/work/down/temp/dpdk/mk/rte.app.mk:399: test] Error 1
make[2]: *** [/work/down/temp/dpdk/mk/rte.subdir.mk:37: test] Error 2
make[1]: *** [/work/down/temp/dpdk/mk/rte.sdkbuild.mk:48: app] Error 2
make: *** [/work/down/temp/dpdk/mk/rte.sdkroot.mk:99: all] Error 2
..
...
This happens on 4.19.4-300.fc29.x86_64.
The error is reproducible and consistent.
It did not happen on previous releases of DPDK (though I don't remember exactly
which)
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-03-09 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-222-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).